Changes between Version 6 and Version 7 of ReleaseProcedure


Ignore:
Timestamp:
Jun 27, 2007, 11:16:04 AM (13 years ago)
Author:
Jari Häkkinen
Comment:

Minor release procedure is done. More needed on patch releases.

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v6 v7  
    2828This section describes what to do when publishing a minor release.
    2929
     30 1. Make sure that all commits are performed into to the trunk, such
     31    as bumping version number(s) ([source:trunk/configure.ac configure.ac]),
     32    acknowledge contributions ([source:trunk/THANKS THANKS]), update
     33    files [source:trunk/NEWS NEWS] and [source:trunk/ChangeLog ChangeLog].
     34    [[br]][[br]]
     35  i. Update version number in `configure.ac`. Locate and change the
     36     below line
     37{{{
     38AC_INIT([[svndigest]],[A.B],[jari.at.thep.lu.se])
     39}}}
     40  i. Update `THANKS`. Remember, ego and vanity is the currency of open
     41     source projects. Well, there are other reasons for open source
     42     projects but `THANKS` is for boosting peoples ego. [[br]][[br]]
     43  i. Set the date for the new release in `NEWS`
     44{{{
     45Version A.B (released 26 June 2007)
     46}}}
     47    Make sure that the items in `NEWS` covers the new features of the
     48    release. [[br]][[br]]
     49  i. Finalize the links to trac in `ChangeLog`
     50{{{
     51version A.B:
     52        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=N&stop_rev=M
     53        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B&order=id
     54}}}
     55  i. Commit changes to the repository, `svn ci -m "Preparing release A.B"`
     56     [[br]][[br]]
    3057 1. Needless to say, make sure that the program is in a state to be
    3158    released; make sure that all the tests pass, test the distribution
     
    3562make check
    3663make distcheck
    37 }}}
    38  1. Make sure that all commits are performed into to the trunk, such
    39     as bumping version number(s) ([source:trunk/configure.ac configure.ac]),
    40     acknowledge contributions ([source:trunk/THANKS THANKS]), update
    41     files [source:trunk/NEWS NEWS] and [source:trunk/ChangeLog ChangeLog]. [[br]][[br]]
    42   i. Set the date for the new release in `NEWS`
    43 {{{
    44 Version A.B (released 26 June 2007)
    4564}}}
    4665 1. Create a tag using a one liner like
     
    6584{{{
    6685svn copy http://lev.thep.lu.se/repository/svndigest/tags/A.B \
    67     http://lev.thep.lu.se/repository/svndigest/branches/A.B \
     86    http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable \
    6887    -m "New patch branch for A.B"
    6988}}}
    7089 1. Check out the new minor branch
    7190{{{
    72 svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B A.B
     91svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable A.B-stable
    7392}}}
     93    and [[br]][[br]]
    7494  i. Edit `NEWS` on trunk to introduce a new section for the upcoming
    7595     release. The section starts with:
    7696{{{
    77 Version A.B.1 (released ?? ????? 200?)
     97Version A.B.1 (released DATE)
    7898}}}
    79      Leave the release date blank for now. It will remain this way
    80      until rolling time.
     99     The date is set when version A.B.1 is released. [[br]][[br]]
    81100  i. Commit change `svn ci -m "add a new NEWS section for upcoming
    82101     A.B.1 release"` [[br]][[br]]
     102 1. Prepare the trunk for the next milestone [[br]][[br]]
     103  i. Update version number in `configure.ac`. Locate and change the
     104     below line
     105{{{
     106AC_INIT([[svndigest]],[preA.[B+1]],[jari.at.thep.lu.se])
     107}}}
     108  i. Add an entry in `NEWS`
     109{{{
     110Version A.[B+1] (released DATE)
     111}}}
     112     The date is set when version A.[B+1] is released. [[br]][[br]]
     113  i. Add an entry in `ChangeLog`
     114{{{
     115version A.[B+1]:
     116        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=[M+1]&stop_rev=HEAD
     117        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.[B+1]&order=id
     118}}}
     119  i. Commit changes to the repository,
     120     `svn ci -m "Changes for future release A.[B+1]"` [[br]][[br]]
    83121 1. Close the [http://lev.thep.lu.se/trac/svndigest/roadmap milestone]
    84122    associated with the release and add a new milestone as needed.
     
    102140 1. Create a tag using a one liner like
    103141{{{
    104 svn copy http://lev.thep.lu.se/repository/svndigest/branch/A.B \
     142svn copy http://lev.thep.lu.se/repository/svndigest/branch/A.B-stable \
    105143    http://lev.thep.lu.se/repository/svndigest/tags/A.B.C \
    106144    -m "Tagging version A.B.C"