Repository: commons-rng
Updated Branches:
  refs/heads/1.0-release f8d230826 -> 412ffb379

Update release process document.


Branch: refs/heads/1.0-release
Commit: 10d4ec69689f42a534eee9474e7b5a756e3a8217
Parents: 2471de8
Author: Gilles <>
Authored: Sun Sep 11 19:35:14 2016 +0200
Committer: Gilles <>
Committed: Sun Sep 11 19:35:14 2016 +0200

 doc/release/release.howto.txt | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
index 12a0a69..b1e1839 100644
--- a/doc/release/release.howto.txt
+++ b/doc/release/release.howto.txt
@@ -201,7 +201,7 @@ Then, assuming the first candidate, the suffix will be 
"RC1" (this should
 be the same as in the "<properties>" in the "pom.xml"), and the command
 will be:
-  $ git tag -s -m "RC1." RNG_1_0_RC1
+  $ git tag -u "__Your_key_id__" -s -m "RC1." RNG_1_0_RC1
 If you have several GPG keys, you may prefer to use "-u keyId" to select a 
 key for signing the tag instead of "-s" which select automatically one key
@@ -220,7 +220,7 @@ You will get something like:
-followed by GPG output lines
+followed by GPG output lines.
 Remember the commit ID listed in the object line (here 
 as it is the most stable reference for traceability.
@@ -244,6 +244,7 @@ currently on any branch. This is expected in this situation.
 Check that the last commit has the id you noted in the previous step:
+  $ cd commons-rng
   $ git log -1
@@ -290,15 +291,15 @@ and their associated fingerprints
 and their signatures
-Note that Nexus automatically adds "md5" and "sha1" checksums files to the 
-files (cryptographic signature). These fingerprints on signatures are spurious
-and have to be manually removed from Nexus staging area.
+Nexus used to add "md5" and "sha1" checksums files to the "asc" files
+(cryptographic signature). If these fingerprints on signatures are
+present, they must be manually removed from Nexus staging area.
 The process also transfers the complete source and binaries distributions 
-  commons-rng-1.0.-bin.tar.gz
-  commons-rng-1.0.-src.tar.gz
+  commons-rng-1.0-bin.tar.gz
+  commons-rng-1.0-src.tar.gz
 as well as their associated .md5 and .sha1 fingerprints and .asc signatures.
 All these files are not maven artifacts but rather distribution archives: They
 belong elsewhere; hence they must also been removed from the Nexus staging
@@ -353,7 +354,7 @@ Then run these commands:
   $ mvn site
   $ cd target
   $ mv site commons-rng-1.0-RC1-site
-  $ lftp s
+  $ lftp s
      lftp> cd public_html
      lftp> mirror -R 
      lftp> bye
@@ -370,13 +371,13 @@ Tag name:
   RNG_1_0_RC1 (signature can be checked from git using 'git tag -v')
 Tag URL:
 Commit ID the tag points at:
-  <>
 Distribution files:
@@ -391,7 +392,7 @@ KEYS file to check signatures:
 Maven artifacts:
 [ ] +1 Release it.
 [ ] +0 Go ahead; I don't care.

Reply via email to