Changes between Version 52 and Version 53 of ReleaseProcedure


Ignore:
Timestamp:
Feb 21, 2010, 8:10:09 PM (13 years ago)
Author:
Peter
Comment:

updated ReleaseProcedure to reflect that we use svn 1.6 server

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v52 v53  
    155155    -m "Tagging version A.B"
    156156}}}
    157  1. Prepare the minor branch for the first patch release [[br]][[br]]
    158   i. Update version number in `m4/version.m4`. Locate and change the
    159      below lines
    160 {{{
    161 m4_define([PATCH_VERSION], [1])
    162 m4_define([DEV_BUILD], [true])
    163 }}}
    164   i. Add an entry in `NEWS`
    165 {{{
    166 version A.B.1 (released NOT YET)
    167 }}}
    168      The date is set when version A.B.1 is released. [[br]][[br]]
    169   i. Commit changes to the repository,
    170      `svn ci -m "Bumping VERSION to A.B.1"` [[br]][[br]]
    171157 1. Upload `yat-A.B.tar.gz` and md5 file to Downloadpage [[br]][[br]]
    172158 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]]
     
    201187    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
    202188    Remember to set the date.[[br]][[br]]
    203  1. If required, merge the minor release into the trunk. To avoid confusion and
     189 1. Merge the minor release into the trunk. To avoid confusion and
    204190    minimize the risk of loosing fixes, this step is only performed by
    205191    the ''Merge Master''. [[br]][[br]]
     
    210196svn status -q
    211197}}}
    212   i. Merge changes into trunk. In this example the difference between a
    213      minor release tag and the first patch release tag is merged into
    214      the trunk WC
    215 {{{
    216 svn merge http://dev.thep.lu.se/yat/svn/branches/A.B-stable@fork_revision \
    217           http://dev.thep.lu.se/yat/svn/tags/A.B\
     198  i. Merge changes into trunk.
     199{{{
     200svn merge http://dev.thep.lu.se/yat/svn/branches/A.B-stable
    218201}}}
    219202  i. Resolve all conflicts. Run tests and perform all other
     
    223206  i. Commit changes to the trunk branch.
    224207{{{
    225 svn commit -m "Merged release A.B to the trunk. Delta A.B - A.B@fork_revision"
    226 }}}
     208svn commit -m "Merged release A.B to the trunk."
     209}}}
     210 1. Prepare the minor branch for the first patch release [[br]][[br]]
     211  i. Update version number in `m4/version.m4`. Locate and change the
     212     below lines
     213{{{
     214m4_define([PATCH_VERSION], [1])
     215m4_define([DEV_BUILD], [true])
     216}}}
     217  i. Add an entry in `NEWS`
     218{{{
     219version A.B.1 (released NOT YET)
     220}}}
     221     The date is set when version A.B.1 is released. [[br]][[br]]
     222  i. Commit changes to the repository,
     223     `svn ci -m "Bumping VERSION to A.B.1"` [[br]][[br]]
    227224
    228225
     
    275272    -m "Tagging version A.B.C"
    276273}}}
    277  1. Prepare the minor branch for the next patch release [[br]][[br]]
    278   i. Update version number in `m4/version.m4`. Locate and change the
    279      below lines
    280 {{{
    281 m4_define([PATCH_VERSION], [C+1])
    282 m4_define([DEV_BUILD], [true])
    283 }}}
    284   i. Update the interface version number in `m4/version.m4`. Locate and change the
    285      below line
    286 {{{
    287 m4_define([YAT_LT_VERSION_INFO], [c:r+1:a])
    288 }}}
    289      i.e., only raise the revision number since the interface will not
    290      change. See the
    291      [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning
    292      libtool manual] for details.[[br]][[br]]
    293   i. Add an entry in `NEWS`
    294 {{{
    295 version A.B.[C+1] (released DATE)
    296 }}}
    297      The date is set when version A.B.[C+1] is released. [[br]][[br]]
    298   i. Commit changes to the repository,
    299      `svn ci -m "Bumping VERSION to A.B.[C+1]"` [[br]][[br]]
    300274 1. Upload `yat-A.B.C.tar.gz` and md5 file to DownloadPage [[br]][[br]]
    301275 1. Update DownloadPage and [wiki:WikiStart WikiStart][[br]][[br]]
     
    338312     the trunk WC
    339313{{{
    340 svn merge http://dev.thep.lu.se/yat/svn/tags/A.B \
    341           http://dev.thep.lu.se/yat/svn/tags/A.B.1
     314svn merge http://dev.thep.lu.se/yat/svn/branches/0.6-stable
    342315}}}
    343316  i. Resolve all conflicts. Run tests and perform all other
     
    347320  i. Commit changes to the trunk branch.
    348321{{{
    349 svn commit -m "Merged patch release A.B.1 to the trunk. Delta A.B.1 - A.B"
    350 }}}
    351 
     322svn commit -m "Merged patch release A.B.1 to the trunk."
     323}}}
     324 1. Prepare the minor branch for the next patch release [[br]][[br]]
     325  i. Update version number in `m4/version.m4`. Locate and change the
     326     below lines
     327{{{
     328m4_define([PATCH_VERSION], [C+1])
     329m4_define([DEV_BUILD], [true])
     330}}}
     331  i. Update the interface version number in `m4/version.m4`. Locate and change the
     332     below line
     333{{{
     334m4_define([YAT_LT_VERSION_INFO], [c:r+1:a])
     335}}}
     336     i.e., only raise the revision number since the interface will not
     337     change. See the
     338     [http://www.gnu.org/software/libtool/manual/html_node/Versioning.html#Versioning
     339     libtool manual] for details.[[br]][[br]]
     340  i. Add an entry in `NEWS`
     341{{{
     342version A.B.[C+1] (released DATE)
     343}}}
     344     The date is set when version A.B.[C+1] is released. [[br]][[br]]
     345  i. Commit changes to the repository,
     346     `svn ci -m "Bumping VERSION to A.B.[C+1]"` [[br]][[br]]