On Feb 2, 2009, at 3:44 PM, Mark Struberg wrote:
Some projects will name their release candidates
and corresponding votes
Or delete the SVN tag and do it again?
The artifacts have not been published yet...
There is a release:rollback mojo which will do all the pom-renaming
back (which is not needed in our case). The tag removal is not
implemented yet (because tag-removal is not supported in maven-
scm-1.1) and has to be done manually. But this is marked as TODO in
the release plugin code, so my guess is that that's the way it
_should_ work.
btw: I would not use -RC1 but only -M1.1, M1.2, etc because I
personally prefer to use the term 'RC' only for release candicates
of final versions.
I got a little carried away implying that the artifacts would contain
the RCx name. Can just be used in the vote/staging directory (unique
prefix, etc). Just letting you know how other projects have handle
this. It's not uncommon to see a RC5 and higher... I think "1.0 RC1"
and a "1.0-M1 RC1" are pretty descriptive and distinct. However, don't
really care... As long as the project knows what is being voted on,
even if we're having multiple rounds of voting, I'm fine...
--kevan
