Update release howto.

Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-rng/commit/70e9c165
Tree: http://git-wip-us.apache.org/repos/asf/commons-rng/tree/70e9c165
Diff: http://git-wip-us.apache.org/repos/asf/commons-rng/diff/70e9c165

Branch: refs/heads/master
Commit: 70e9c1655ffd9544a56dc29d12d16caf5d589407
Parents: 070cbc0
Author: Gilles <er...@apache.org>
Authored: Tue Dec 13 01:30:27 2016 +0100
Committer: Gilles <er...@apache.org>
Committed: Tue Dec 13 01:30:27 2016 +0100

----------------------------------------------------------------------
 doc/release/release.howto.txt | 57 ++++++++++++++++----------------------
 1 file changed, 24 insertions(+), 33 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/commons-rng/blob/70e9c165/doc/release/release.howto.txt
----------------------------------------------------------------------
diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
index b9caa43..63205f1 100644
--- a/doc/release/release.howto.txt
+++ b/doc/release/release.howto.txt
@@ -566,49 +566,40 @@ Put the official final tag to point at the same commit as 
the last release candi
 
 
 (22)
-Clean up files and prepare for next version (here we assume it will be 1.1):
+Switch back to the "master" branch.
+We now prepare for the next round of development (here we assume that the
+next version will be 1.1).
 
-Edit "doap_rng.rdf" to add the just released version date.
-It is located at
-  https://svn.apache.org/repos/asf/commons/cms-site/trunk/doap
-in the SVN repository.
+  (22a)
+  Edit "doap_rng.rdf" to add the just released version date.
+  It is located at
+    https://svn.apache.org/repos/asf/commons/cms-site/trunk/doap
+  in the SVN repository.
 
-Edit every "pom.xml" file (i.e. for each module) to contain
+  (22b)
+  Retrieve files from the "1.0-release branch" (so that the web site will
+  contain up-to-date information):
 
-  <version>1.1-SNAPSHOT</version>
+    $ git checkout 1.0-release src/site/xdoc/download_rng.xml
+    $ git checkout 1.0-release src/changes/changes.xml
 
-Edit "src/changes/changes.xml" to add a new section for the next release,
-setting the release date to "TBD" and the description to the empty string.
+  Edit "src/changes/changes.xml" to add a new section for the next release,
+  setting the release date and description to "TBD".
+  Then commit them.
 
-Double-check that the "pom.xml" files *really* have a "-SNAPSHOT" suffix
-in the "<version>" property.
-Then commit everything:
+  (22c)
+  Edit every "pom.xml" file (i.e. for each module) to contain
 
-  $ git add \
-      doap_rng.rdf \
-      src/changes/changes.xml \
-      pom.xml \
-      commons-rng-client-api/pom.xml \
-      commons-rng-core/pom.xml \
-      commons-rng-simple/pom.xml \
-      commons-rng-sampling/pom.xml \
-      commons-rng-jmh/pom.xml \
-      commons-rng-examples/pom.xml \
-      dist-archive/pom.xml
+    <version>1.1-SNAPSHOT</version>
 
-  $ git commit -m "Preparing next version (1.1)"
-  $ git push
+  Double-check that the "pom.xml" files *really* have a "-SNAPSHOT" suffix
+  in the "<version>" property.
+  Then commit them.
 
+  Push everything to the Apache repository.
 
-(23)
-Switch back to branch "master" and merge the "1.0-release" branch
-
-  $ git checkout master
-  $ git merge 1.0-release
-  $ git push
 
-
-(24)
+(23)
 Allow for the web site mirrors to be updated (possibly several hours); then
 send (from your apache account) a release announcement to the following ML:
   annou...@apache.org

Reply via email to