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 msicker: https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=29&rev2=30 Comment: add info about git and other things learned Once you've done this, take the following steps to perform a release: 1. Edit {{{pom.xml}}} and change the {{{Log4jReleaseVersion}}} property to the version you are releasing. - 1. Check out from https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk. + 1. Make a fresh Git clone of the master branch of {{{https://git-wip-us.apache.org/repos/asf/logging-log4j2.git}}} 1. Update {{{src/changes/announcement.vm}}} 1. Run {{{mvn -P release-notes generate-resources}}} to create the release notes. 1. Update {{{src/changes/changes.xml}}} with the release date. @@ -61, +61 @@ a. Create the email addressed to [email protected] and [email protected]. Sending the email to the PMC is not strictly necessary, but due to the small size of the logging PMC it is expedient to do so in order to get the required votes. a. Copy the changes in the release from {{{RELEASE-NOTES.txt}}} into the email. a. Provide a link to the tag, web site on http://people.apache.org, and the artifacts in the Nexus repository. - a. Provide the command to download all the artifacts: {{{wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate $LINK}}} where {{{$LINK}}} is the URL to the repository you just closed. + a. Provide the command to download all the artifacts: {{{wget -e robots=off --cut-dirs=3 -r -p -np --no-check-certificate $LINK}}} where {{{$LINK}}} is the URL to the repository you just closed (plus the {{{org/apache/logging/log4j/}}} path appended). - a. Provide a list of the artifacts by copying from the email notification sent from the Nexus Repository. + a. Provide a list of the artifacts by copying from the email notification sent from the Nexus Repository.<<FootNote(Nexus has not been sending this email for the past few releases at least)>> 1. If the release vote fails proceed as described in the section below, otherwise if it passes: a. Download all the distribution files from the Nexus repository (you can download using the wget above and then going to the distribution sub-directory). a. Rename the distribution files back to their original names (Maven renamed them when they were deployed to Nexus) using {{{for f in log4j-distribution-*; do mv $f $(echo $f | sed 's/^log4j-distribution-/apache-log4j-/g'); done}}} @@ -85, +85 @@ a. Commit the delete to Subversion. a. See ManagingTheWebSite regarding sub-projects. a. Copy the release web site from the local directory where it was deployed into the sub-project directory and make it be the current link. - 1. After the website is updated, send the release announcement email. + 1. After the website is updated, send the release announcement email. This should be sent out to [email protected], [email protected], [email protected], and [email protected] + {{{#!wiki warning + '''Warning''' + + Git tags are immutable and behave rather differently than Subversion. + }}} If the release fails before 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. Delete the release tag in subversion. + 1. Delete the release tag in Git. 1. Reset the version numbers in all of the poms back to the release snapshot. 1. Restart the release process as the same release candidate. 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 subversion to add {{{rcn}}} to the end of the tag. + 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''' 1. Reset the version numbers in all of the poms back to the release snapshot. 1. Restart the release process as a new release candidate.
