Changes between Version 41 and Version 42 of ReleaseProcedure


Ignore:
Timestamp:
Dec 19, 2008, 8:16:06 PM (12 years ago)
Author:
Peter
Comment:

references ticket #472

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v41 v42  
    3232=== Creating a release branch ===
    3333
    34 Once people agree that a new release branch should be made, the ''Release Manager'' creates it with the following procedure (substitute A.B with the version you are preparing, ''e.g.'' 0.3, or 1.0):
     34Once people agree that a new release branch should be made, the
     35''Release Manager'' creates it with the following procedure
     36(substitute A.B with the version you are preparing, ''e.g.'' 0.3, or
     371.0):
    3538
    3639 1. Update copyright statements with command:
     
    6568  i. Commit changes to the repository,
    6669     `svn ci -m "Changes for future release A.[B+1]"` [[br]][[br]]
     70 1. When someone with access to documentation site has time available,
     71 they will upgrade to the new branch. This person is usually not the
     72 release manager, so please send a reminder.
    6773
    6874=== Rolling a minor release ===
     
    139145    -m "Tagging version A.B"
    140146}}}
    141  1. Update the version list in Trac using the
    142     [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
    143     Remember to set the date.[[br]][[br]]
    144147 1. Prepare the minor branch for the first patch release [[br]][[br]]
    145148  i. Update version number in `build_support/version.m4`. Locate and change the
     
    186189  i. In section '''yat ''devel'' ''' update link to `[milestone:A.B+1 A.B+1]`.[[br]][[br]]
    187190  i. On WikiStart update links `[source:tags/A.B/NEWS NEWS]`.[[br]][[br]]
    188   i. Generate documentation to new version of yat, and update link on WikiStart.[[br]][[br]]
     191 1. Close the [http://dev.thep.lu.se/yat/roadmap milestone] associated
     192    with the release and replace `head` with appropriate revision. Add
     193    a new milestone as needed (with log link).
     194 1. Update the version list in Trac using the
     195    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
     196    Remember to set the date.[[br]][[br]]
    189197 1. If required, merge the minor release into the trunk. To avoid confusion and
    190198    minimize the risk of loosing fixes, this step is only performed by
     
    216224}}}
    217225    Remove `trunk_merge` if it was created. [[br]][[br]]
    218  1. Close the [http://dev.thep.lu.se/yat/roadmap milestone]
    219     associated with the release and replace `head` with appropriate revision. Add a new milestone as needed (with log link).
    220226
    221227
     
    287293    -m "Tagging version A.B.C"
    288294}}}
    289  1. Update the version list in Trac using the
    290     [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
    291     Remember to set the date.[[br]][[br]]
     295 1. Prepare the minor branch for the next patch release [[br]][[br]]
     296  i. Update version number in `build_support/version.m4`. Locate and change the
     297     below lines
     298{{{
     299m4_define([PATCH_VERSION], [C+1])
     300m4_define([DEV_BUILD], [true])
     301}}}
     302  i. Update the interface version number in `build_support/version.m4`. Locate and change the
     303     below line
     304{{{
     305m4_define([YAT_LT_REVISION], [r+1])
     306}}}
     307     i.e., only raise the revision number since the interface was not changed. See the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
     308  i. Add an entry in `NEWS`
     309{{{
     310version A.B.[C+1] (released DATE)
     311}}}
     312     The date is set when version A.B.[C+1] is released. [[br]][[br]]
     313  i. Add an entry in `ChangeLog`
     314{{{
     315version A.B.[C+1]:
     316        - http://dev.thep.lu.se/yat/log/branches/A.B-stable?rev=HEAD&stop_rev=[M+1]
     317        - http://dev.thep.lu.se/yat/query?milestone=A.B.[C+1]&order=id
     318}}}
     319  i. Commit changes to the repository,
     320     `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]]
    292321 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]]
    293322  i. Update the section '''Latest stable release''' to reflect the new
     
    307336     `[milestone:A.B.[C+1] A.B.[C+1]]`.[[br]][[br]]
    308337  i. On WikiStart update reference to explicit latest version number, and `[source:tags/A.B/NEWS NEWS]`.[[br]][[br]]
    309   i. Generate documentation to new version of yat, and update link on WikiStart.[[br]][[br]]
    310  1. Prepare the minor branch for the next patch release [[br]][[br]]
    311   i. Update version number in `build_support/version.m4`. Locate and change the
    312      below lines
    313 {{{
    314 m4_define([PATCH_VERSION], [C+1])
    315 m4_define([DEV_BUILD], [true])
    316 }}}
    317   i. Update the interface version number in `build_support/version.m4`. Locate and change the
    318      below line
    319 {{{
    320 m4_define([YAT_LT_REVISION], [r+1])
    321 }}}
    322      i.e., only raise the revision number since the interface was not changed. See the [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning libtool manual] for details.[[br]][[br]]
    323   i. Add an entry in `NEWS`
    324 {{{
    325 version A.B.[C+1] (released DATE)
    326 }}}
    327      The date is set when version A.B.[C+1] is released. [[br]][[br]]
    328   i. Add an entry in `ChangeLog`
    329 {{{
    330 version A.B.[C+1]:
    331         - http://dev.thep.lu.se/yat/log/branches/A.B-stable?rev=HEAD&stop_rev=[M+1]
    332         - http://dev.thep.lu.se/yat/query?milestone=A.B.[C+1]&order=id
    333 }}}
    334   i. Commit changes to the repository,
    335      `svn ci -m "Changes for future release A.B.[C+1]"` [[br]][[br]]
     338 1. Close the milestone associated with the release, replace `head`
     339    with appropriate revision in log link, set diff to
     340    '`diff:tags/A.B.[C-1]//tags/A.B.C/`'. Create a log link,
     341    '`log:branches/A.B-stable@TAG-REVISION:head`', and diff,
     342    '`diff:tags/A.B.C//branches/A.B-stable/`', in milestone associated
     343    with next patch release.
     344 1. Update the version list in Trac using the
     345    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
     346    Remember to set the date.[[br]][[br]]
    336347 1. Merge the patch release into the trunk. To avoid confusion and
    337348    minimize the risk of loosing fixes, this step is only performed by
     
    362373}}}
    363374    Remove `trunk_merge` if it was created. [[br]][[br]]
    364  1. Close the milestone associated with the release, replace `head` with appropriate revision in log link,
    365     set diff to '`diff:tags/A.B.[C-1]//tags/A.B.C/`'. Create a log link, '`log:branches/A.B-stable@TAG-REVISION:head`',
    366     and diff, '`diff:tags/A.B.C//branches/A.B-stable/`', in milestone associated with next patch release.
    367