[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

Apache Wiki
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=40&rev2=41

      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.
+     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*}}}.
@@ -92, +92 @@

      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 [hidden email], [hidden email], [hidden email], and [hidden email]
 
- {{{#!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. Revert any changes that have not been committed.
-  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 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.#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.
 
Loading...