Changes between Version 7 and Version 8 of ReleaseProcedure


Ignore:
Timestamp:
Jun 27, 2007, 12:39:18 PM (13 years ago)
Author:
Jari Häkkinen
Comment:

patch release procedure done except for merging.

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v7 v8  
    1 == Publishing a release ==
     1= Publishing a release =
    22
    33These instructions cover how to release minor and patch releases in a
     
    2424
    2525
    26 === Minor release procedure ===
     26== Minor release procedure ==
    2727
    2828This section describes what to do when publishing a minor release.
     
    4343  i. Set the date for the new release in `NEWS`
    4444{{{
    45 Version A.B (released 26 June 2007)
     45version A.B (released 26 June 2007)
    4646}}}
    4747    Make sure that the items in `NEWS` covers the new features of the
     
    7878make dist
    7979}}}
    80     Publish the new package and make the appropriate changes to the
    81     [http://lev.thep.lu.se/trac/svndigest/wiki/DownloadPage download page].
    82     Remove `A.B_dist` directory. [[br]][[br]]
    83  1. Create a new minor release branch using a one liner like
     80    Attach the new package to the DownloadPage.  Remove `A.B_dist`
     81    directory. [[br]][[br]]
     82 1. Update DownloadPage [[br]][[br]]
     83  i. Update the section '''Latest stable release''' to reflect the new
     84     version, that is [[br]][[br]]
     85   * Change the version number [[br]][[br]]
     86   * Update the package link to the new version [[br]][[br]]
     87   * Update link to NEWS file to `source:tags/A.B/NEWS` [[br]][[br]]
     88  i. In section '''svndigest ''latest release'' ''' update link to
     89     `[source:tags/A.B/NEWS NEWS]` and modify the svn command to
     90{{{
     91svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B svndigest-A.B
     92}}}
     93  i. In section '''svndigest ''stable'' ''' update link to
     94     `[milestone:A.B A.B]` and modify the svn command to
     95{{{
     96svn checkout http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable svndigest-A.B
     97}}}
     98 1. Create a new minor branch using a one liner like
    8499{{{
    85100svn copy http://lev.thep.lu.se/repository/svndigest/tags/A.B \
     
    87102    -m "New patch branch for A.B"
    88103}}}
    89  1. Check out the new minor branch
    90 {{{
    91 svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable A.B-stable
    92 }}}
    93     and [[br]][[br]]
    94   i. Edit `NEWS` on trunk to introduce a new section for the upcoming
    95      release. The section starts with:
    96 {{{
    97 Version A.B.1 (released DATE)
     104 1. Prepare the minor branch for the first patch release [[br]][[br]]
     105  i. Check out the new minor branch
     106{{{
     107svn co http://lev.thep.lu.se/repository/svndigest/branches/A.B-stable A.B
     108}}}
     109  i. Update version number in `configure.ac`. Locate and change the
     110     below line
     111{{{
     112AC_INIT([[svndigest]],[preA.B.1],[jari.at.thep.lu.se])
     113}}}
     114  i. Add an entry in `NEWS`
     115{{{
     116version A.B.1 (released DATE)
    98117}}}
    99118     The date is set when version A.B.1 is released. [[br]][[br]]
    100   i. Commit change `svn ci -m "add a new NEWS section for upcoming
    101      A.B.1 release"` [[br]][[br]]
    102  1. Prepare the trunk for the next milestone [[br]][[br]]
     119  i. Add an entry in `ChangeLog`
     120{{{
     121version A.B.1:
     122        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=[M+1]&stop_rev=HEAD
     123        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.1&order=id
     124}}}
     125  i. Commit changes to the repository,
     126     `svn ci -m "Changes for future release A.B.1"` [[br]][[br]]
     127 1. Prepare the trunk for the next minor release [[br]][[br]]
    103128  i. Update version number in `configure.ac`. Locate and change the
    104129     below line
     
    108133  i. Add an entry in `NEWS`
    109134{{{
    110 Version A.[B+1] (released DATE)
     135version A.[B+1] (released DATE)
    111136}}}
    112137     The date is set when version A.[B+1] is released. [[br]][[br]]
     
    123148
    124149
    125 === Patch release procedure ===
     150
     151== Patch release procedure ==
    126152
    127153This section describes what to do when publishing a patch release.
    128154
     155 1. Make sure that all commits are performed into to the trunk, such
     156    as bumping version number(s) (`configure.ac`), acknowledge
     157    contributions (`THANKS`), update files `NEWS` and
     158    `ChangeLog`. [[br]][[br]]
     159  i. Update version number in `configure.ac`. Locate and change the
     160     below line
     161{{{
     162AC_INIT([[svndigest]],[A.B.C],[jari.at.thep.lu.se])
     163}}}
     164  i. Update `THANKS`. [[br]][[br]]
     165  i. Set the date for the new release in `NEWS`
     166{{{
     167version A.B.C (released 27 June 2007)
     168}}}
     169    Make sure that the items in `NEWS` covers the new features of the
     170    release. [[br]][[br]]
     171  i. Finalize the links to trac in `ChangeLog`
     172{{{
     173version A.B.C:
     174        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=N&stop_rev=M
     175        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.C&order=id
     176}}}
     177  i. Commit changes to the repository, `svn ci -m "Preparing release A.B.C"`
     178     [[br]][[br]]
    129179 1. Needless to say, make sure that the program is in a state to be
    130180    released; make sure that all the tests pass, test the distribution
     
    135185make distcheck
    136186}}}
    137  1. Make sure that all commits are performed into to the trunk, such
    138     as bumping version number(s) (configure.ac), acknowledge
    139     contributions (THANKKS), update NEWS and !ChangeLog. [[br]][[br]]
    140187 1. Create a tag using a one liner like
    141188{{{
     
    153200make dist
    154201}}}
    155     Publish the new package and make the appropriate changes to the
    156     [http://lev.thep.lu.se/trac/svndigest/wiki/DownloadPage download page].
    157     Remove `A.B.C_dist` directory. [[br]][[br]]
     202    Attach the new package to the DownloadPage. Remove `A.B.C_dist`
     203    directory. [[br]][[br]]
     204 1. Update DownloadPage [[br]][[br]]
     205  i. Update the section '''Latest stable release''' to reflect the new
     206     version, that is [[br]][[br]]
     207   * Change the version number [[br]][[br]]
     208   * Update the package link to the new version [[br]][[br]]
     209   * Update link to NEWS file to `source:tags/A.B.C/NEWS` [[br]][[br]]
     210  i. In section '''svndigest ''latest release'' ''' update link to
     211     `[source:tags/A.B.C/NEWS NEWS]` and modify the svn command to
     212{{{
     213svn checkout http://lev.thep.lu.se/repository/svndigest/tags/A.B.C svndigest-A.B.C
     214}}}
     215  i. In section '''svndigest ''stable'' ''' update link to
     216     `[milestone:A.B.[C+1] A.B.[C+1]]`. [[br]][[br]]
     217 1. Prepare the minor branch for the next release [[br]][[br]]
     218  i. Update version number in `configure.ac`. Locate and change the
     219     below line
     220{{{
     221AC_INIT([[svndigest]],[preA.B.[C+1]],[jari.at.thep.lu.se])
     222}}}
     223  i. Add an entry in `NEWS`
     224{{{
     225version A.B.[C+1] (released DATE)
     226}}}
     227     The date is set when version A.B.[C+1] is released. [[br]][[br]]
     228  i. Add an entry in `ChangeLog`
     229{{{
     230version A.B.[C+1]:
     231        - http://lev.thep.lu.se/trac/svndigest/log/trunk?rev=[M+1]&stop_rev=HEAD
     232        - http://lev.thep.lu.se/trac/svndigest/query?milestone=A.B.[C+1]&order=id
     233}}}
     234  i. Commit changes to the repository,
     235     `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]]
    158236 1. Merge the patch tag into the trunk. To avoid confusion and
    159237    minimize the risk of loosing fixes, this step is only performed by
    160     a Merge Master. [[br]][[br]]
     238    the Merge Master. [[br]][[br]]
    161239  i. Checkout a pristine version of the trunk.
    162240{{{
     
    171249  i. Resolve all conflicts. Run tests and perform all other
    172250     appropriate tests to make sure that the merge does not create
    173      havoc.
     251     havoc. [[br]][[br]]
    174252  i. Commit changes to trunk.
    175253{{{