Changes between Version 7 and Version 8 of ReleaseProcedure

Timestamp:

Jun 27, 2007, 12:39:18 PM (15 years ago)

Author:

Jari Häkkinen

Comment:

patch release procedure done except for merging.

ReleaseProcedure

@@ -1 @@
-== Publishing a release ==
+= Publishing a release =
 
 These instructions cover how to release minor and patch releases in a
@@ -24 +24 @@
 
 
-=== Minor release procedure ===
+== Minor release procedure ==
 
 This section describes what to do when publishing a minor release.
@@ -43 +43 @@
   i. Set the date for the new release in `NEWS`
 {{{
-Version A.B (released 26 June 2007)
+version A.B (released 26 June 2007)
 }}}
     Make sure that the items in `NEWS` covers the new features of the
@@ -78 +78 @@
 make dist
 }}}
-    Publish the new package and make the appropriate changes to the
-    [http://lev.thep.lu.se/trac/svndigest/wiki/DownloadPage download page].
-    Remove `A.B_dist` directory. [[br]][[br]]
- 1. Create a new minor release branch using a one liner like
+    Attach the new package to the DownloadPage.  Remove `A.B_dist`
+    directory. [[br]][[br]]
+ 1. Update DownloadPage [[br]][[br]]
+  i. Update the section '''Latest stable release''' to reflect the new
+     version, that is [[br]][[br]]
+   * Change the version number [[br]][[br]]
+   * Update the package link to the new version [[br]][[br]]
+   * Update link to NEWS file to `source:tags/A.B/NEWS` [[br]][[br]]
+  i. In section '''svndigest ''latest release'' ''' update link to
+     `[source:tags/A.B/NEWS NEWS]` and modify the svn command to
+{{{
+svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B svndigest-A.B
+}}}
+  i. In section '''svndigest ''stable'' ''' update link to
+     `[milestone:A.B A.B]` and modify the svn command to
+{{{
+svn checkout http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable svndigest-A.B
+}}}
+ 1. Create a new minor branch using a one liner like
 {{{
 svn copy http://lev.thep.lu.se/repository/svndigest/tags/A.B \
@@ -87 +102 @@
     -m "New patch branch for A.B"
 }}}
- 1. Check out the new minor branch
-{{{
-svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable A.B-stable
-}}}
-    and [[br]][[br]]
-  i. Edit `NEWS` on trunk to introduce a new section for the upcoming
-     release. The section starts with:
-{{{
-Version A.B.1 (released DATE)
+ 1. Prepare the minor branch for the first patch release [[br]][[br]]
+  i. Check out the new minor branch
+{{{
+svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable A.B
+}}}
+  i. Update version number in `configure.ac`. Locate and change the
+     below line
+{{{
+AC_INIT([[svndigest]],[preA.B.1],[jari.at.thep.lu.se])
+}}}
+  i. Add an entry in `NEWS`
+{{{
+version A.B.1 (released DATE)
 }}}
      The date is set when version A.B.1 is released. [[br]][[br]]
-  i. Commit change `svn ci -m "add a new NEWS section for upcoming
-     A.B.1 release"` [[br]][[br]]
- 1. Prepare the trunk for the next milestone [[br]][[br]]
+  i. Add an entry in `ChangeLog`
+{{{
+version A.B.1:
+        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=[M+1]&stop_rev=HEAD
+        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.1&order=id
+}}}
+  i. Commit changes to the repository,
+     `svn ci -m "Changes for future release A.B.1"` [[br]][[br]]
+ 1. Prepare the trunk for the next minor release [[br]][[br]]
   i. Update version number in `configure.ac`. Locate and change the
      below line
@@ -108 +133 @@
   i. Add an entry in `NEWS`
 {{{
-Version A.[B+1] (released DATE)
+version A.[B+1] (released DATE)
 }}}
      The date is set when version A.[B+1] is released. [[br]][[br]]
@@ -123 +148 @@
 
 
-=== Patch release procedure ===
+
+== Patch release procedure ==
 
 This section describes what to do when publishing a patch release.
 
+ 1. Make sure that all commits are performed into to the trunk, such
+    as bumping version number(s) (`configure.ac`), acknowledge
+    contributions (`THANKS`), update files `NEWS` and
+    `ChangeLog`. [[br]][[br]]
+  i. Update version number in `configure.ac`. Locate and change the
+     below line
+{{{
+AC_INIT([[svndigest]],[A.B.C],[jari.at.thep.lu.se])
+}}}
+  i. Update `THANKS`. [[br]][[br]]
+  i. Set the date for the new release in `NEWS`
+{{{
+version A.B.C (released 27 June 2007)
+}}}
+    Make sure that the items in `NEWS` covers the new features of the
+    release. [[br]][[br]]
+  i. Finalize the links to trac in `ChangeLog`
+{{{
+version A.B.C:
+        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=N&stop_rev=M
+        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id
+}}}
+  i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
+     [[br]][[br]]
  1. Needless to say, make sure that the program is in a state to be
     released; make sure that all the tests pass, test the distribution
@@ -135 +185 @@
 make distcheck
 }}}
- 1. Make sure that all commits are performed into to the trunk, such
-    as bumping version number(s) (configure.ac), acknowledge
-    contributions (THANKKS), update NEWS and !ChangeLog. [[br]][[br]]
  1. Create a tag using a one liner like
 {{{
@@ -153 +200 @@
 make dist
 }}}
-    Publish the new package and make the appropriate changes to the
-    [http://lev.thep.lu.se/trac/svndigest/wiki/DownloadPage download page].
-    Remove `A.B.C_dist` directory. [[br]][[br]]
+    Attach the new package to the DownloadPage. Remove `A.B.C_dist`
+    directory. [[br]][[br]]
+ 1. Update DownloadPage [[br]][[br]]
+  i. Update the section '''Latest stable release''' to reflect the new
+     version, that is [[br]][[br]]
+   * Change the version number [[br]][[br]]
+   * Update the package link to the new version [[br]][[br]]
+   * Update link to NEWS file to `source:tags/A.B.C/NEWS` [[br]][[br]]
+  i. In section '''svndigest ''latest release'' ''' update link to
+     `[source:tags/A.B.C/NEWS NEWS]` and modify the svn command to
+{{{
+svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B.C svndigest-A.B.C
+}}}
+  i. In section '''svndigest ''stable'' ''' update link to
+     `[milestone:A.B.[C+1] A.B.[C+1]]`. [[br]][[br]]
+ 1. Prepare the minor branch for the next release [[br]][[br]]
+  i. Update version number in `configure.ac`. Locate and change the
+     below line
+{{{
+AC_INIT([[svndigest]],[preA.B.[C+1]],[jari.at.thep.lu.se])
+}}}
+  i. Add an entry in `NEWS`
+{{{
+version A.B.[C+1] (released DATE)
+}}}
+     The date is set when version A.B.[C+1] is released. [[br]][[br]]
+  i. Add an entry in `ChangeLog`
+{{{
+version A.B.[C+1]:
+        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=[M+1]&stop_rev=HEAD
+        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.[C+1]&order=id
+}}}
+  i. Commit changes to the repository,
+     `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]]
  1. Merge the patch tag into the trunk. To avoid confusion and
     minimize the risk of loosing fixes, this step is only performed by
-    a Merge Master. [[br]][[br]]
+    the Merge Master. [[br]][[br]]
   i. Checkout a pristine version of the trunk.
 {{{
@@ -171 +249 @@
   i. Resolve all conflicts. Run tests and perform all other
      appropriate tests to make sure that the merge does not create
-     havoc.
+     havoc. [[br]][[br]]
   i. Commit changes to trunk.
 {{{