Changes between Version 4 and Version 5 of ReleaseProcedure

Timestamp:

Aug 16, 2007, 10:04:05 AM (17 years ago)

Author:

Jari Häkkinen

Comment:

Working on ticket:656. This is the last draft before actually trying the procedures.

ReleaseProcedure

@@ -94 +94 @@
 svn co http://lev.thep.lu.se/repository/base/branches/A.B-stable A.B
 }}}
-  i. Update version number in `build.xml`. Locate and change to the
+  i. Update version number in `build.xml`. Locate and change the
      below line
 {{{
@@ -136 +136 @@
 This section describes what to do when publishing a patch release A.B.C.
 
- 1. Make sure that all commits are performed into to the branch, 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` cover all important bug fixes of the
-    release. [[br]][[br]]
-  i. Finalize the links to trac in `ChangeLog`
-{{{
-version A.B.C:
-        - http://trac.thep.lu.se/trac/svndigest/log/branches/A.B-stable?rev=N&stop_rev=M
-        - http://trac.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id
-}}}
-  where `N` is given by 
-{{{
-$ svn update
-N-2
-}}}
-  and `M` should have been set at previous release.[[br]][[br]]
+ 1. Make sure that all commits are performed into to the trunk, such
+    as bumping version number(s) ([source:trunk/build.xml build.xml]),
+    acknowledge contributions ([source:trunk/credits.txt credits.txt]),
+    API changes that may affect backwards compatibility
+    ([http://base.thep.lu.se/chrome/site/doc/html/appendix/appendix.incompatible.html API changes]),
+    and other files as necessary.
+    [[br]][[br]]
+  i. Update version number in `build.xml`. Locate and change the
+     below line
+{{{
+<property name="base.maintenanceversion" value="C" />
+}}}
+  i. Update `credits.txt`. [[br]][[br]]
+  i. Make sure that the API incompatibility list is up to date
+     [http://base.thep.lu.se/chrome/site/doc/html/appendix/appendix.incompatible.html API changes].
+     This document should really be changed as the API changes, please do not leave this task to be
+     done at the last minute of release. [[br]][[br]]
+  i. Make other changes as needed. If items are missing from this list, please add them with proper
+     instructions for the items changes maintenance. [[br]][[br]]
   i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
      [[br]][[br]]
- 1. Update copyright statements with commands
-{{{
-./bootstrap
-make all
-make check
+ 1. Update copyright statements with
+{{{
 ./bin/svndigest --copyright
 }}}
- Examine the updates and commit changes with `svn ci -m "updating copyright statements"`.[[br]][[br]]
+    Examine the updates and commit changes with `svn ci -m "updating copyright statements"`. For
+    this step [http://trac.thep.lu.se/trac/svndigest svndigest] is obviously needed. [[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
@@ -179 +168 @@
     appropriate:
 {{{
-./bootstrap
-make check
-make distcheck
-}}}
+Please add test command sequence here
+}}}
+    If you fail in this step, please resolve the issues and restart these procedures. [[br]][[br]]
  1. Create a tag using a one liner like
 {{{
-svn copy http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
-    http://lev.thep.lu.se/repository/svndigest/tags/A.B.C \
+svn copy http://lev.thep.lu.se/repository/BASE/branches/A.B-stable \
+    http://lev.thep.lu.se/repository/base/tags/A.B.C \
     -m "Tagging version A.B.C"
 }}}
  1. Update the version list in Trac using the
-    [http://lev.thep.lu.se/trac/svndigest/admin trac-admin tool].
+    [http://lev.thep.lu.se/trac/base/admin trac-admin tool].
     [[br]][[br]]
  1. Create a distribution package:
 {{{
-svn co http://lev.thep.lu.se/repository/svndigest/tags/A.B.C A.B.C_dist
+svn co http://lev.thep.lu.se/repository/base/tags/A.B.C A.B.C_dist
 cd A.B.C_dist
-./bootstrap
-./configure [OPTION]...
-make dist
-}}}
-    Attach the new package to the DownloadPage. Remove `A.B.C_dist`
-    directory. [[br]][[br]]
- 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]]
+ant package
+}}}
+    Upload the new packages to the download are (Currently `~jari/www/base` directory).
+    Remove `A.B.C_dist` directory. [[br]][[br]]
+ 1. Prepare the minor branch for the next patch release [[br]][[br]]
+  i. Update version number in `build.xml`. Locate and change the
+     below line
+{{{
+<property name="base.maintenanceversion" value="[C+1]" />
+}}}
+  i. Commit changes to the repository,
+     `svn ci -m "Changes for future release A.B.[C+1]"` [[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
+   * Update the package links to the new version [[br]][[br]]
+  i. In section '''base ''latest release'' ''' modify the svn command to
+{{{
+svn checkout http://lev.thep.lu.se/repository/base/tags/A.B.C base-A.B.C
+}}}
+  i. In section '''base ''stable'' ''' update link to
      `[milestone:A.B.[C+1] A.B.[C+1]]`.[[br]][[br]]
-  i. On WikiStart update links `[source:tags/A.B/doc/readme.txt Manual]`, `[source:tags/A.B/NEWS NEWS]`, and `[source:tags/A.B/INSTALL Install]`, .[[br]][[br]] 
- 1. Prepare the minor branch for the next patch 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://trac.thep.lu.se/trac/svndigest/log/branches/A.B-stable?rev=HEAD&stop_rev=[M+1]
-        - http://trac.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 release into the trunk. To avoid confusion and
     minimize the risk of loosing fixes, this step is only performed by
-    the Merge Master. [[br]][[br]]
+    the Merge Master. (Johan Enell is currently Merge Master and as the master
+    he knows what he is doing.) [[br]][[br]]
   i. Checkout a pristine version of the trunk.
 {{{
-svn checkout http://lev.thep.lu.se/repository/svndigest/trunk trunk_merge
+svn checkout http://lev.thep.lu.se/repository/base/trunk trunk_merge
 }}}
   i. Merge changes into trunk. In this example the diffence between a
@@ -252 +225 @@
   i. Resolve all conflicts. Run tests and perform all other
      appropriate tests to make sure that the merge does not create
-     havoc. [[br]][[br]]
+     havoc. (run !TestAll and perform an installation.) [[br]][[br]]
   i. Commit changes to the trunk branch.
 {{{
 svn commit -m "Merged patch release A.B.1 to the trunk. Delta A.B.1 - A.B"
 }}}
- 1. Close the milestone associated with the release and replace `head` with appropriate revision in log link. Add a new
-    milestone as needed (with a log link).
+ 1. ''Performing this step is to acnkowledge that the merge has been performed.'' [[br]]
+    Close the milestone associated with the release and replace `head` with appropriate
+    revision in log link. Add a new milestone as needed (with an associated log link like
+    ''Revision Log: log:branches/webservices@3001:head'' in the description field).