If you take the optimistic view (as I do when I am release manager) that you will only need a single release candidate than this method means you never have to rename a tag. I see no real difference between what you are saying is correct and what the wiki says except for the delete operation. Both make a copy of the tag. However, in the way it is currently written, the tag is only copied when a failure occurs, so even if there is some problem the only thing that is lost is a tag to a failed RC. When the release is good no copying takes place so you can be sure the tag is what you voted on.
Ralph > On Oct 20, 2014, at 2:34 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > This is not good idea IMO because you have now deleted the tag we voted on > and full traceability from the VOTE email is harder. Over at Commons, we copy > a successful 1.2.3-RCn tag to 1.2.3. Nothing lost and it is lightweight. > > Gary > > > -------- Original message -------- > From: Apache Wiki > Date:10/20/2014 00:17 (GMT-05:00) > To: Apache Wiki > Subject: [Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers > > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Logging Wiki" for > change notification. > > The "Log4j2ReleaseGuide" page has been changed by RalphGoers: > https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=30&rev2=31 > > If the release fails after sending the vote email: > 1. Login to http://repository.apache.org using your ASF credentials. > Select "Staging Repositories" then check the org.apache.logging repository > and drop it. > 1. Rename the release tag in Git to add {{{rcn}}} to the end of the tag. > '''Note that this may not be possible in Git depending on configuration''' > + {{{ > + git tag log4j-n.n log4j-n.n-rcn > + git tag -d log4j-n.n > + git push origin :refs/tags/log4j-n.n > + git push --tags > + }}} > - 1. Reset the version numbers in all of the poms back to the release > snapshot. > + 1.#3 Reset the version numbers in all of the poms back to the release > snapshot. > 1. Restart the release process as a new release candidate. > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org