Changes between Version 3 and Version 4 of ReleaseProcedure


Ignore:
Timestamp:
Jun 25, 2007, 10:14:28 PM (13 years ago)
Author:
Peter Johansson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v3 v4  
    1313  1.  Edit `NEWS` on trunk to introduce a new section for the upcoming release. The section starts with:
    1414{{{
    15 Version A.B (released ?? ????? 200X)
     15Version A.B (released ?? ????? 200?)
    1616}}}
    1717  Leave the release date blank for now. It will remain this way until rolling time.
     
    3333This section describes how to roll a release A.B.C.
    3434
    35   1. Update files `NEWS` and `configure.ac` on release branch
     35  1. Update files `ChangeLog`, `NEWS`, and `configure.ac` on release branch
    3636    *  Add text in `NEWS` what is new for this release
    3737    *  Update `configure.ac` setting ''devel'' to `false`
     
    6767    * Commit changes to trunk: `svn commit -m "Merged log:branches/0.1-stable#N:M trunk."`
    6868
    69   7. Update version in `configure.ac` on release branch to A.B.(C++).
    70 
    71   8.  Edit NEWS on trunk (and release branch) to introduce a new section for the upcoming release. The section starts with:
     69  7.  Edit NEWS on trunk (and release branch) to introduce a new section for the upcoming release. The section starts with:
    7270{{{
    7371Version A.B.0 (released ?? ????? 200?)
     
    7573  Leave the release date blank for now. It will remain this way until rolling time.
    7674
    77   9. Update Trac:
     75  8. Update Trac:
    7876    * Update the version list in Trac using the trac-admin tool, i.e., add version A.B
    7977    * Close the milestone A.B and add a new milestones.