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 <div>-------- Original message --------</div><div>From: Apache Wiki <wikidi...@apache.org> </div><div>Date:10/20/2014 00:17 (GMT-05:00) </div><div>To: Apache Wiki <wikidi...@apache.org> </div><div>Subject: [Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers </div><div> </div>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.