[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

[Apache Wiki <wi...@apache.org>]

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=43&rev2=44

   1. Check out the release tag that was created via the Maven release plugin using {{{git checkout tags/tagname}}}.
   1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn site:stage -DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
   1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}}. Commit the site to your github.io account. 
+  1. Copy the distribution archive files from log4j-distribution/target to where https://dist.apache.org/repos/dist/dev/logging/log4j/ is checked out on your machine.
+     a. Generate the md5 checksum of the bin and source archive files using {{{md5 apache-log4j-2.x-site.zip > apache-log4j-2.x-xxx.zip.md5}}}, {{{md5sum apache-log4j-2.x-xxx.zip > apache-log4j-2.x-xxx.zip.md4}}}, or {{{gpg --print-md MD5 apache-log4j-2.x-xxx.zip > apache-log4j-2.x-xxx.zip.md5}}}.
+     a. Generate the sha1 checksum of the bin and source archive files using {{{sha apache-log4j-2.x-site.zip > apache-log4j-2.x-xxx.zip.sha1}}}, {{{shasum apache-log4j-2.x-xxx.zip > apache-log4j-2.x-xxx.zip.sha1}}}, or {{{gpg --print-md SHA1 apache-log4j-2.x-xxx.zip > apache-log4j-2.x-xxx.zip.sha1}}}.
+  1. Add the site zip to where https://dist.apache.org/repos/dist/dev/logging/log4j/ is checked out on your machine.
+     a. Sign the site ZIP file using {{{gpg --armor --output apache-log4j-2.x-site.zip.asc --detach-sig apache-log4j-2.x-site.zip}}}. You can use the {{{--local-user [key ID]}}} option (it must come before {{{--detach-sig}}}) to specify the exact key to use when signing the ZIP file.
+     a. Generate the md5 checksum of the site ZIP using {{{md5 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md5}}}, {{{md5sum apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md4}}}, or {{{gpg --print-md MD5 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md5}}}.
+     a. Generate the sha1 checksum of the site zip using {{{sha apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}, {{{shasum apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}, or {{{gpg --print-md SHA1 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}.
   1. Generate the release vote email:
-     a. Create the email addressed to log4j-dev@logging.apache.org and private@logging.apache.org. 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. Create the email addressed to dev@logging.apache.org. Sending the email to the PMC is not necessary.
      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 (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.<<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. Create a new tag named log4j-n.n from the log4j-n.n-rcn tag by changing to the changing to the directory containing the source for the release and performing {{{git tag -a log4j-n.n -m "Release n.n of Log4j"}} followed by {{{git push --tags}}}
-     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}}}
-     a. Delete the {{{*.asc.md5}}} and {{{*.asc.sha1}}} files and {{{*.pom*}}}.
-     a. Copy the site ZIP file you created earlier to the distribution release directory.  
-     a. Sign the site ZIP file using {{{gpg --armor --output apache-log4j-2.x-site.zip.asc --detach-sig apache-log4j-2.x-site.zip}}}. You can use the {{{--local-user [key ID]}}} option (it must come before {{{--detach-sig}}}) to specify the exact key to use when signing the ZIP file.
-     a. Generate the md5 checksum of the site ZIP using {{{md5 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md5}}}, {{{md5sum apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md4}}}, or {{{gpg --print-md MD5 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.md5}}}.
-     a. Generate the sha1 checksum of the site zip using {{{sha apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}, {{{shasum apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}, or {{{gpg --print-md SHA1 apache-log4j-2.x-site.zip > apache-log4j-2.x-site.zip.sha1}}}.
   1. The following steps must be performed by a PMC member:
      a. Checkout https://dist.apache.org/repos/dist/release/logging/log4j. 
      a. Create the release directory under the {{{log4j}}} directory.
-     a. Move all the distribution artifacts to that directory.
+     a. Move all the distribution artifacts from the distribution dev location to that directory.
      a. Perform an {{{svn add}}} of the release directory.
      a. Commit the release to Subversion.
      a. Login to reporter.apache.org and add the release version and date.
   1. The following steps can then be taken by whomever started the release:
-     a. Delete the distribution, samples and perf directories from the Nexus repository.
+     a. Delete the core-its project from the Nexus repository.
      a. Release the remaining artifacts in the Nexus Repository.
   1. Wait 12-24 hours (or after the distribution artifacts have been propagated to the mirrors and the Maven artifacts have been propagated to the Central Repository), and then the following steps must be performed by a PMC member:
      a. Perform {{{svn delete}}} on the '''''previous''''' release directory for the same version under the {{{log4j}}} directory (https://dist.apache.org/repos/dist/release/logging/log4j).
      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. This should be sent out to log4j-dev@logging.apache.org, log4j-user@logging.apache.org, private@logging.apache.org, and general@logging.apache.org
+  1. After the website is updated, send the release announcement email. This should be sent out to dev@logging.apache.org, log4j-user@logging.apache.org, private@logging.apache.org, and general@logging.apache.org.
+  2. Send the release announcement to announcements@apache.org using your apache.org email address.
  
  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.