Think the idea was to avoid to have a tag which can have been checked out already but fundamentally agree there is no point to have such a rule and it just makes the project handling hard with no benefit in practise.
Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-06 19:11 GMT+01:00 Thomas Vandahl <[email protected]>: > On 06.11.17 04:48, Gary Gregory wrote: >> The document http://commons.apache.org/releases/prepare.html clearly shows >> an example of an RC tag being labeled with the "RC1" postfix. > > Not in the maven-release-plugin chapter. And with reason. The problem of > the later copy would be, that the tagged pom.xml contains the pathes to > the tag created originally (read: with the RC suffix) so that if you > checkout the copied tag (read: the release version), the settings in > pom.xml will still point to the RC tag. > > Therefore, with a Maven build you should always create the release > version, tag it, vote on it and let it be. If the vote fails, the tag > can as well be removed. What's the point of keeping it around? The vote > failed, after all. The tag is invalid anyway. > > BTW, using the SVN revisions given in the vote mail (this is why they > are important), you can always access the failed RC tag, ok? > > Bye, Thomas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
