(logging-log4cxx) 01/01: Improve instructions for releasing Log4cxx

[sw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

swebb2066 pushed a commit to branch update_release__instructions
in repository https://gitbox.apache.org/repos/asf/logging-log4cxx.git

commit 2cfa94de38b25584d598a1db40622944e249974c
Author: Stephen Webb <sw...@gmail.com>
AuthorDate: Wed Nov 27 15:12:43 2024 +1100

    Improve instructions for releasing Log4cxx
---
 admin/releasing.md | 6 +++++-
 admin/staging.md   | 6 ++----
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/admin/releasing.md b/admin/releasing.md
index 9325c107..14ce0a2a 100644
--- a/admin/releasing.md
+++ b/admin/releasing.md
@@ -12,6 +12,8 @@ Prerequisites
 * The web-site for the new version has been published to https://logging.staged.apache.org/log4cxx (using [this procedure](staging.md) )
 * An e-mail has been sent to dev@logging.apache.org announcing the intention to release
 * Your e-mail client can send mail from your `@apache.org` address. (Refer: https://eventmesh.apache.org/community/how-to-use-email/)
+* You have generated a RSA key of length 2048 or more (Refer: https://infra.apache.org/release-signing.html)
+* You have practiced signing files for weeks or months (to ensure you remember your passphrase)
 * Your public key is available in [Apache Logging KEYS file](https://dist.apache.org/repos/dist/release/logging/KEYS)
 
 Steps
@@ -19,6 +21,8 @@ Steps
 
 1. Tag HEAD as the release candidate
     - `git checkout master`
+    - `git pull`
+    - `git tag v1.3.1-RC1`
     - `git push origin tag v1.3.1-RC1`
 1. Remove the old artifacts from svn
     - `svn co https://dist.apache.org/repos/dist/dev/logging -N apache-dist-logging-dev`
@@ -41,7 +45,7 @@ Steps
         - The browser will download the file `Upload release files.zip` onto your system
 1. Unpack the release files using these commands (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory)
     - `unzip "$HOME/Downloads/Upload release files.zip"`
-1. Sign release artifacts (Refer: https://infra.apache.org/release-signing.html) (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory)
+1. Sign release artifacts (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory)
     - `gpg --armor --output apache-log4cxx-1.3.1.zip.asc --detach-sig apache-log4cxx-1.3.1.zip`
     - `gpg --armor --output apache-log4cxx-1.3.1.tar.gz.asc --detach-sig apache-log4cxx-1.3.1.tar.gz`
 1. Send the new artifacts to svn (with `apache-dist-logging-dev/log4cxx/1.3.1` as the working directory)
diff --git a/admin/staging.md b/admin/staging.md
index 741ede5a..bb306f28 100644
--- a/admin/staging.md
+++ b/admin/staging.md
@@ -45,15 +45,13 @@ Steps to add a new version to the Log4cxx web site
     - `cd /tmp/log4cxx-site`
     - `git checkout asf-staging`
 1. Use the newly generated files for the web site documentation
-    - `git rm -r 1.3.1`
     - `mv /tmp/build/src/site/html /tmp/log4cxx-site/1.3.1`
     - `git add 1.3.1`
 1. Update the symbolic links in the base of the web site working directory
     - `cd /tmp/log4cxx-site`
-    - `rm latest_stable old_stable`
-    - `ln -s 1.3.1 latest_stable`
+    - `rm old_stable`
     - `ln -s 1.2.0 old_stable`
-    - `git add latest_stable old_stable`
+    - `git add old_stable`
 1. Update `.htaccess` so the final `RewriteRule` redirects to the new version
     - `RewriteRule ^(.*)$     /log4cxx/1.3.1/$1      [R=temp,L]`
     - `git add .htaccess`