Changes between Version 1 and Version 2 of ReleaseProcedure


Ignore:
Timestamp:
Jun 25, 2007, 8:45:49 PM (13 years ago)
Author:
Peter Johansson
Comment:

setting project name to svndigest

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v1 v2  
    22= Release Procedure =
    33
    4 Pandai uses "MAJOR.MINOR.PATCH" release numbers, with the same guidelines as APR (see http://apr.apache.org/versioning.html).
     4Svndigest uses "MAJOR.MINOR.PATCH" release numbers, with the same guidelines as APR (see http://apr.apache.org/versioning.html).
    55
    66=== Creating a release branch ===
     
    1313  1.  Edit `NEWS` on trunk to introduce a new section for the upcoming release. The section starts with:
    1414{{{
    15 Version A.B.0 (released ?? ????? 200X, from /branches/A.B-stable)
    16       http://lev.thep.lu.se/repository/pandai/tags/A.B
     15Version A.B (released ?? ????? 200X, from /branches/A.B-stable)
     16      http://lev.thep.lu.se/repository/svndigest/tags/release-A.B
    1717}}}
    1818  Leave the release date blank for now. It will remain this way until rolling time.
     
    2222  3.  Create a new release branch using a one liner like
    2323{{{
    24   svn copy http://lev.thep.lu.se/repository/pandai/trunk \
    25            http://lev.thep.lu.se/repository/pandai/branches/A.B-stable \
    26            -m "New branch for Pandai A.B.x"
     24  svn copy http://lev.thep.lu.se/repository/svndigest/trunk \
     25           http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
     26           -m "New branch for svndigest A.B.x"
    2727}}}
    2828
     
    4343  3. Create a tag with
    4444{{{
    45   svn copy . http://lev.thep.lu.se/repository/pandai/tags/A.B \
     45  svn copy . http://lev.thep.lu.se/repository/svndigest/tags/A.B \
    4646           -m "Tagging version A.B.C"
    4747}}}
     
    5050    * Upload gzipped tar file and update corresponding link.
    5151    * Update link to NEWS file to `source:tags/A.B.C/NEWS`
    52     * In ''Pandai latest release'' update to `[source:tags/A.B.C/NEWS NEWS]` and modify svn command to 
    53       `svn checkout http://lev.thep.lu.se/repository/pandai/tags/A.B.C pandai-A.B.C`
    54     * In ''Pandai stable'' update link to `[milestone:A.B.(C++) A.B.(C++)]dev` and modify svn command to
    55       `svn checkout http://lev.thep.lu.se/repository/pandai/branches/A.B-stable pandai-A.B.(C++)dev`
    56     * In ''Pandai devel'' modify svn command to
    57       `svn checkout http://lev.thep.lu.se/repository/pandai/trunk pandai-A.(B++).0dev`
     52    * In ''Svndigest latest release'' update to `[source:tags/A.B.C/NEWS NEWS]` and modify svn command to 
     53      `svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B.C svndigest-A.B.C`
     54    * In ''Svndigest stable'' update link to `[milestone:A.B.(C++) A.B.(C++)]dev` and modify svn command to
     55      `svn checkout http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable svndigest-A.B.(C++)dev`
     56    * In ''Svndigest devel'' modify svn command to
     57      `svn checkout http://lev.thep.lu.se/repository/svndigest/trunk svndigest-A.(B++).0dev`
    5858
    5959  5. Set ''devel'' to `true` in `configure.ac`.
     
    6464    * Find head revision (M) in release branch: `svn info | grep Rev:`
    6565    * `cd path/to/trunk`
    66     * `svn merge -r N:M http://lev.thep.lu.se/repository/pandai/branches/A.B-stable`
     66    * `svn merge -r N:M http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable`
    6767    * Run `make check` to make sure that the merge succeeded.
    6868    * Commit changes to trunk: `svn commit -m "Merged log:branches/0.1-stable#N:M trunk."`
     
    7373{{{
    7474Version A.B.0 (released ?? ????? 200X, from /branches/A.B-stable)
    75       http://lev.thep.lu.se/repository/pandai/tags/A.B.(C++)
     75      http://lev.thep.lu.se/repository/svndigest/tags/A.B.(C++)
    7676}}}
    7777  Leave the release date blank for now. It will remain this way until rolling time.