created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ (rev 1814438)
Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-06 20:46 GMT+01:00 Gary Gregory <[email protected]>: > On Mon, Nov 6, 2017 at 11:11 AM, Thomas Vandahl <[email protected]> wrote: > >> 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. >> > > The tag should not be removed. Ever. Look in svn and git and you will see > tags for every RC ever created. > > If you want to change the release requirements, well, that's another story. > Feel free to start a separate thread for that. For now I urge you to follow > the current release process. Yes, it is ponderous and requires many steps, > but creating a tag is not the biggest pain point. > > Gary > > >> 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]
