[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers
Dear wiki user,
You have subscribed to a wiki page "Logging Wiki" for change notification.
The page "Log4j2ReleaseGuide" has been deleted by RalphGoers:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=44&rev2=45
- = Log4j 2.x Release Process =
- Before beginning your first release, take the following preparatory steps:
-
- 1. Run {{{mvn clean install}}} on the project to make sure it will build
cleanly.
- 1. Run {{{mvn -P rat -DskipTests verify}}} to verify all the licenses are
valid.
- 1. Login to http://repository.apache.org using your ASF credentials. Click
on your username in the upper-right-hand corner and click Profile. Make sure
your email address is correct. If not, contact Infra to get it corrected. You
will be unable to get the necessary notifications until it's corrected.
- 1. Make sure you have a 4096-bit RSA PGP key pair for code signing. The
public key should be published in a public repository, preferably
http://pgp.mit.edu/. Also make sure the public key is published to
http://www.apache.org/dist/logging/KEYS.
- 1. Edit {{{~/.m2/settings.xml}}} to add the corresponding private key and
its passphrase to your settings. Also add the Apache Subversion server
credentials and Sonatype repository credentials to your settings (this is your
ASF credentials). You'll want to blank out the passphrase after each release
and fill it back in prior to each release so that it isn't compromised.
- ~-{{{#!xml
-
-
- apache-release
-
- ABC123FC
- thisIsMyPassphrase
- gpg2
-
-
-
-
-
- apache-release
-
-
- ...
-
-
-
- svn.apache.org
- myUsername
- myPassword
-
-
- apache.releases.https
- myUsername
- myPassword
-
-
- apache.snapshots.https
- myUsername
- myPassword
-
-
- }}}-~
-
- 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. 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.
- 1. Pick a logo from src/site/resources/logos. Edit it with Gimp to add the
release version number and save it as a png. Copy the saved logo to
src/site/resources/images/logo.png.
- 1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated along with the other files
that were modified.
- 1. Run {{{mvn site}}} followed by {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory and
verify that the site looks good.
- 1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}}
to start the release. Enter the password to your signing key when prompted.
- 1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
- 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
{{{--de
[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=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-...@logging.apache.org and
priv...@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 d...@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.<>
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 usi
[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=42&rev2=43
1. Run {{{mvn -P release-notes generate-resources}}} to create the release
notes.
1. Update {{{src/changes/changes.xml}}} with the release date.
1. Pick a logo from src/site/resources/logos. Edit it with Gimp to add the
release version number and save it as a png. Copy the saved logo to
src/site/resources/images/logo.png.
- 1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
+ 1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated along with the other files
that were modified.
1. Run {{{mvn site}}} followed by {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory and
verify that the site looks good.
1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}}
to start the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
[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=41&rev2=42
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.
+ 1. Pick a logo from src/site/resources/logos. Edit it with Gimp to add the
release version number and save it as a png. Copy the saved logo to
src/site/resources/images/logo.png.
1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
1. Run {{{mvn site}}} followed by {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory and
verify that the site looks good.
1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}}
to start the release. Enter the password to your signing key when prompted.
[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=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.<>
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 log4j-...@logging.apache.org,
log4j-u...@logging.apache.org, priv...@logging.apache.org, and
general@logging.apache.org
- {{{#!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.
[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=39&rev2=40
Before beginning your first release, take the following preparatory steps:
+ 1. Run {{{mvn clean install}}} on the project to make sure it will build
cleanly.
+ 1. Run {{{mvn -P rat -DskipTests verify}}} to verify all the licenses are
valid.
1. Login to http://repository.apache.org using your ASF credentials. Click
on your username in the upper-right-hand corner and click Profile. Make sure
your email address is correct. If not, contact Infra to get it corrected. You
will be unable to get the necessary notifications until it's corrected.
1. Make sure you have a 4096-bit RSA PGP key pair for code signing. The
public key should be published in a public repository, preferably
http://pgp.mit.edu/. Also make sure the public key is published to
http://www.apache.org/dist/logging/KEYS.
1. Edit {{{~/.m2/settings.xml}}} to add the corresponding private key and
its passphrase to your settings. Also add the Apache Subversion server
credentials and Sonatype repository credentials to your settings (this is your
ASF credentials). You'll want to blank out the passphrase after each release
and fill it back in prior to each release so that it isn't compromised.
@@ -52, +54 @@
1. Run {{{mvn -P release-notes generate-resources}}} to create the release
notes.
1. Update {{{src/changes/changes.xml}}} with the release date.
1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
+ 1. Run {{{mvn site}}} followed by {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory and
verify that the site looks good.
1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}}
to start the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
1. Check out the release tag that was created via the Maven release plugin
using {{{git checkout tags/tagname}}}.
[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=38&rev2=39
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
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}}}
and copy to your account at {{{people.apache.org}}} with {{{scp log4j.zip
myusern...@people.apache.org:/home/myUsername}}}. Unzip the contents into your
public html directory.
+ 1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}}.
Commit the site to your github.io account.
1. Generate the release vote email:
a. Create the email addressed to log4j-...@logging.apache.org and
priv...@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. Copy the changes in the release from {{{RELEASE-NOTES.txt}}} into the
email.
[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=37&rev2=38
1. Run {{{mvn -P release-notes generate-resources}}} to create the release
notes.
1. Update {{{src/changes/changes.xml}}} with the release date.
1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
- 1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT}}} to start the release.
Enter the password to your signing key when prompted.
+ 1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}}
to start the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
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.
@@ -64, +64 @@
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.<>
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. 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*}}}.
[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=36&rev2=37
a. Move all the distribution artifacts 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. Release the remaining artifacts in the Nexus Repository.
[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=35&rev2=36
a. Perform an {{{svn add}}} of the release directory.
a. Commit the release to Subversion.
1. The following steps can then be taken by whomever started the release:
- a. Delete the distribution directory from the Nexus repository.
+ a. Delete the distribution, samples and perf directories 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).
[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=34&rev2=35
1. Run {{{mvn -P release-notes generate-resources}}} to create the release
notes.
1. Update {{{src/changes/changes.xml}}} with the release date.
1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
- 1. Run {{{mvn -P apache-release release:prepare release:perform}}} to start
the release. Enter the password to your signing key when prompted.
+ 1. Run {{{mvn -P apache-release release:prepare release:perform
-DreleaseVersion=n.n -DdevelopmentVersion=n.n-SNAPSHOT}}} to start the release.
Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
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.
[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=33&rev2=34
1. Run {{{mvn -P apache-release release:prepare release:perform}}} to start
the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
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:-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
+ 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}}}
and copy to your account at {{{people.apache.org}}} with {{{scp log4j.zip
myusern...@people.apache.org:/home/myUsername}}}. Unzip the contents into your
public html directory.
1. Generate the release vote email:
a. Create the email addressed to log4j-...@logging.apache.org and
priv...@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.
[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=32&rev2=33
1. Run {{{mvn -P apache-release release:prepare release:perform}}} to start
the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
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-deploy -DstagingSiteURL=file:///$HOME/log4j}}} where {{{$HOME}}} is
your home directory.
+ 1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn
site:-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}}
and copy to your account at {{{people.apache.org}}} with {{{scp log4j.zip
myusern...@people.apache.org:/home/myUsername}}}. Unzip the contents into your
public html directory.
1. Generate the release vote email:
a. Create the email addressed to log4j-...@logging.apache.org and
priv...@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.
[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=31&rev2=32
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.
- 1. Run {{{svn commit}}} to commit the {{{RELEASE-NOTES.txt}}} file that was
just generated.
+ 1. Run {{{git add, git commit, and git push}}} to commit the
{{{RELEASE-NOTES.txt}}} file that was just generated.
1. Run {{{mvn -P apache-release release:prepare release:perform}}} to start
the release. Enter the password to your signing key when prompted.
1. Login to http://repository.apache.org using your ASF credentials. Select
"Staging Repositories" then check the {{{org.apache.logging}}} repository and
close it.
- 1. Check out the release tag that was created via the Maven release plugin.
+ 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-deploy -DstagingSiteURL=file:///$HOME/log4j}}} where {{{$HOME}}} is
your home directory.
1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}}
and copy to your account at {{{people.apache.org}}} with {{{scp log4j.zip
myusern...@people.apache.org:/home/myUsername}}}. Unzip the contents into your
public html directory.
1. Generate the release vote email:
[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.
