Changes between Version 41 and Version 42 of ReleaseProcedure

Timestamp:

Dec 19, 2008, 8:16:06 PM (14 years ago)

Author:

Peter

Comment:

references ticket #472

ReleaseProcedure

@@ -32 +32 @@
 === Creating a release branch ===
 
-Once people agree that a new release branch should be made, the ''Release Manager'' creates it with the following procedure (substitute A.B with the version you are preparing, ''e.g.'' 0.3, or 1.0): 
+Once people agree that a new release branch should be made, the
+''Release Manager'' creates it with the following procedure
+(substitute A.B with the version you are preparing, ''e.g.'' 0.3, or
+1.0):
 
  1. Update copyright statements with command:
@@ -65 +68 @@
   i. Commit changes to the repository,
      `svn ci -m "Changes for future release A.[B+1]"` [[br]][[br]]
+ 1. When someone with access to documentation site has time available, 
+ they will upgrade to the new branch. This person is usually not the 
+ release manager, so please send a reminder.
 
 === Rolling a minor release ===
@@ -139 +145 @@
     -m "Tagging version A.B"
 }}}
- 1. Update the version list in Trac using the
-    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
-    Remember to set the date.[[br]][[br]]
  1. Prepare the minor branch for the first patch release [[br]][[br]]
   i. Update version number in `build_support/version.m4`. Locate and change the
@@ -186 +189 @@
   i. In section '''yat ''devel'' ''' update link to `[milestone:A.B+1 A.B+1]`.[[br]][[br]]
   i. On WikiStart update links `[source:tags/A.B/NEWS NEWS]`.[[br]][[br]] 
-  i. Generate documentation to new version of yat, and update link on WikiStart.[[br]][[br]]
+ 1. Close the [http://dev.thep.lu.se/yat/roadmap milestone] associated
+    with the release and replace `head` with appropriate revision. Add
+    a new milestone as needed (with log link).
+ 1. Update the version list in Trac using the
+    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
+    Remember to set the date.[[br]][[br]]
  1. If required, merge the minor release into the trunk. To avoid confusion and
     minimize the risk of loosing fixes, this step is only performed by
@@ -216 +224 @@
 }}}
     Remove `trunk_merge` if it was created. [[br]][[br]]
- 1. Close the [http://dev.thep.lu.se/yat/roadmap milestone]
-    associated with the release and replace `head` with appropriate revision. Add a new milestone as needed (with log link).
 
 
@@ -287 +293 @@
     -m "Tagging version A.B.C"
 }}}
- 1. Update the version list in Trac using the
-    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
-    Remember to set the date.[[br]][[br]]
+ 1. Prepare the minor branch for the next patch release [[br]][[br]]
+  i. Update version number in `build_support/version.m4`. Locate and change the
+     below lines
+{{{
+m4_define([PATCH_VERSION], [C+1])
+m4_define([DEV_BUILD], [true])
+}}}
+  i. Update the interface version number in `build_support/version.m4`. Locate and change the
+     below line
+{{{
+m4_define([YAT_LT_REVISION], [r+1])
+}}}
+     i.e., only raise the revision number since the interface was not changed. See the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
+  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://dev.thep.lu.se/yat/log/branches/A.B-stable?rev=HEAD&stop_rev=[M+1]
+        - http://dev.thep.lu.se/yat/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. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]]
   i. Update the section '''Latest stable release''' to reflect the new
@@ -307 +336 @@
      `[milestone:A.B.[C+1] A.B.[C+1]]`.[[br]][[br]]
   i. On WikiStart update reference to explicit latest version number, and `[source:tags/A.B/NEWS NEWS]`.[[br]][[br]] 
-  i. Generate documentation to new version of yat, and update link on WikiStart.[[br]][[br]]
- 1. Prepare the minor branch for the next patch release [[br]][[br]]
-  i. Update version number in `build_support/version.m4`. Locate and change the
-     below lines
-{{{
-m4_define([PATCH_VERSION], [C+1])
-m4_define([DEV_BUILD], [true])
-}}}
-  i. Update the interface version number in `build_support/version.m4`. Locate and change the
-     below line
-{{{
-m4_define([YAT_LT_REVISION], [r+1])
-}}}
-     i.e., only raise the revision number since the interface was not changed. See the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
-  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://dev.thep.lu.se/yat/log/branches/A.B-stable?rev=HEAD&stop_rev=[M+1]
-        - http://dev.thep.lu.se/yat/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. Close the milestone associated with the release, replace `head`
+    with appropriate revision in log link, set diff to
+    '`diff:tags/A.B.[C-1]//tags/A.B.C/`'. Create a log link,
+    '`log:branches/A.B-stable@TAG-REVISION:head`', and diff,
+    '`diff:tags/A.B.C//branches/A.B-stable/`', in milestone associated
+    with next patch release.
+ 1. Update the version list in Trac using the
+    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
+    Remember to set the date.[[br]][[br]]
  1. Merge the patch release into the trunk. To avoid confusion and
     minimize the risk of loosing fixes, this step is only performed by
@@ -362 +373 @@
 }}}
     Remove `trunk_merge` if it was created. [[br]][[br]]
- 1. Close the milestone associated with the release, replace `head` with appropriate revision in log link, 
-    set diff to '`diff:tags/A.B.[C-1]//tags/A.B.C/`'. Create a log link, '`log:branches/A.B-stable@TAG-REVISION:head`', 
-    and diff, '`diff:tags/A.B.C//branches/A.B-stable/`', in milestone associated with next patch release.
-