Use strict build tag strategy for 2.0.0 release
Currently Metacat relies on a number of external projects and repositories. We should take this opportunity to finalize many of those projects as true "releases" and do away with the "release candidate" tags that Metacat is using to build.
External SVN project dependencies include:
-eml schema 2.1.1 (tags/RELEASE_EML_2_1_1_RC_2)
-eml style sheets (tags/RELEASE_EML_UTILS_1_0_0_RC13)
Not to forget the d1 jars:
-DataONE v1.0.0 jars (2 API jars + supporting libraries)
Proposed tags. Please comment.
-eml schema 2.1.1 (tags/RELEASE_EML_2_1_1)
-eml style sheets (tags/RELEASE_EML_UTILS_1_0_0)
okay, that's simple enough to have agreed on!
there is an Ecogrid change needed
updating the title to reflect bug as a reminder to remove "RC" from any of the tags we build the release from...
I've merged the Ecogrid RC5 changes to trunk and now am using RC6 that was made from trunk (make sense?).
Should be fine in SEEK/Ecogrid now.
Utilities is now pulling from the final tag.
EML has a schema and a style tag -- those are still at RC level.
I've updated all the tags that Metacat uses during its build process.
Original Bugzilla ID was 5532
Also available in: Atom