Changes between Version 3 and Version 4 of ReleaseProcedure

Timestamp:

Jun 25, 2007, 10:14:28 PM (16 years ago)

Author:

Peter Johansson

Comment:

--

ReleaseProcedure

@@ -13 +13 @@
   1.  Edit `NEWS` on trunk to introduce a new section for the upcoming release. The section starts with: 
 {{{
-Version A.B (released ?? ????? 200X)
+Version A.B (released ?? ????? 200?)
 }}}
   Leave the release date blank for now. It will remain this way until rolling time.
@@ -33 +33 @@
 This section describes how to roll a release A.B.C.
 
-  1. Update files `NEWS` and `configure.ac` on release branch
+  1. Update files `ChangeLog`, `NEWS`, and `configure.ac` on release branch
     *  Add text in `NEWS` what is new for this release
     *  Update `configure.ac` setting ''devel'' to `false`
@@ -67 +67 @@
     * Commit changes to trunk: `svn commit -m "Merged log:branches/0.1-stable#N:M trunk."` 
 
-  7. Update version in `configure.ac` on release branch to A.B.(C++).
-
-  8.  Edit NEWS on trunk (and release branch) to introduce a new section for the upcoming release. The section starts with: 
+  7.  Edit NEWS on trunk (and release branch) to introduce a new section for the upcoming release. The section starts with: 
 {{{
 Version A.B.0 (released ?? ????? 200?)
@@ -75 +73 @@
   Leave the release date blank for now. It will remain this way until rolling time.
 
-  9. Update Trac: 
+  8. Update Trac: 
     * Update the version list in Trac using the trac-admin tool, i.e., add version A.B
     * Close the milestone A.B and add a new milestones.