Changes between Version 61 and Version 62 of ReleaseProcedure


Ignore:
Timestamp:
Oct 31, 2011, 5:43:44 AM (10 years ago)
Author:
Peter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcedure

    v61 v62  
    5353 1. Update copyright statements with command:
    5454{{{
    55 svncopyright -v
     55make copyright
    5656}}}
    5757 Examine the updates and commit
    5858 changes with `svn ci -m "updating copyright statements"`.  For this
    59  step [http://dev.thep.lu.se/svndigest svncopyright] is obviously
     59 step [http://dev.thep.lu.se/svndigest svncopyright] is
    6060 needed.[[br]][[br]]
    6161 1. Create a new minor branch using a one liner like
     
    6565 1. Check out a WC from the newly created branch
    6666{{{
    67 svn co http://dev.thep.lu.se/yat/svn/branches/A.B-stable yat-A.B
     67svn co ^/branches/A.B-stable ../yat-A.B.x
    6868}}}
    6969 1. Copy the svndigest cache from trunk WC to branch WC
    7070{{{
    71 svndigest-copy-cache -v -r /path/to/yat-trunk -t /path/to/yat-A.B
     71svndigest-copy-cache -v -r . -t ../yat-A.B.x
    7272}}}
    7373   which needs svndigest 0.8 or newer.[[br]][[br]]
     
    123123 1. Update copyright statements with command:
    124124{{{
    125 svncopyright -v
     125make copyright
    126126}}}
    127127 Examine the updates and commit changes with `svn ci -m "updating copyright statements"`.
    128  For this step [http://dev.thep.lu.se/svndigest svndigest] is obviously needed.[[br]][[br]]
     128 For this step [http://dev.thep.lu.se/svndigest svndigest] is needed.[[br]][[br]]
    129129 1. Needless to say, make sure that the program is in a state to be
    130130    released; make sure that all the tests pass, test the distribution
    131131    package, and perform all other release tests you think is
    132132    appropriate:[[br]][[br]]
     133    Inspect script tag_and_release.sh and create a config.txt if needed.
    133134    Run
    134135{{{
    135136make all
    136 make release
     137./build_support/tag_and_release.sh
    137138}}}
    138139    Fix potential problems.[[br]][[br]]
    139  1. Check that you are synchronized with repository
    140 {{{
    141 svn status -q -u
    142 }}}
    143  and then create a tag using a one liner like
    144 {{{
    145 svn copy ^/branches/A.B-stable ^/tags/A.B -m "Tagging version A.B"
    146 }}}
    147  1. Upload `yat-A.B.tar.gz` and md5 file to [https://sourceforge.net/downloads/libyat/ sourceforge]
    148     using `scp` like
    149 {{{
    150 scp yat-A.B.tar.gz yat-A.B.tar.gz.MD5 USER,libyat@frs.sourceforge.net:/home/frs/project/l/li/libyat/.
    151 }}}
    152140 1. Update SubversionCheckout and WikiStart[[br]][[br]]
    153141  i. In section '''yat ''latest release'' ''' update link to
     
    175163 1. Update the version list in Trac using the
    176164    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
     165 1. Use `announcement.txt` as template and send email to libyat-users@lists.sourceforge.net
    177166 1. Merge the minor release into the trunk. To avoid confusion and
    178167    minimize the risk of loosing fixes, this step is only performed by
     
    234223 1. Update copyright statements with command:
    235224{{{
    236 svncopyright -v
     225make copyright
    237226}}}
    238227 Examine the updates and commit changes with `svn ci -m "updating copyright statements"`.
     
    242231    package, and perform all other release tests you think is
    243232    appropriate:[[br]][[br]]
     233    Inspect script tag_and_release.sh and create a config.txt if needed.
    244234    Run
    245235{{{
    246236make all
    247 make release
     237./build_support/tag_and_release.sh
    248238}}}
    249239    Fix potential problems.[[br]][[br]]
    250  1. Create a tag, but first check that you are synchronized with repository
    251 {{{
    252 svn status -q -u
    253 }}}
    254  and then create a tag using a one liner like
    255 {{{
    256 svn copy ^/branches/A.B-stable ^/tags/A.B.C -m "Tagging version A.B.C"
    257 }}}
    258  1. Upload `yat-A.B.C.tar.gz` and md5 file to [https://sourceforge.net/downloads/libyat/ sourceforge]
    259     using `scp` like
    260 {{{
    261 scp yat-A.B.C.tar.gz yat-A.B.C.tar.gz.MD5 USER,libyat@frs.sourceforge.net:/home/frs/project/l/li/libyat/.
    262 }}}
    263240 1. Update SubversionCheckout and [wiki:WikiStart WikiStart][[br]][[br]]
    264241  i. In section '''yat ''latest release'' ''' update link to
     
    282259    [http://dev.thep.lu.se/yat/admin/ticket/versions trac-admin tool].
    283260    Remember to set the date.[[br]][[br]]
     261 1. Use `announcement.txt` as template and send email to libyat-users@lists.sourceforge.net
    284262 1. Merge the patch release into the trunk. To avoid confusion and
    285263    minimize the risk of loosing fixes, this step is only performed by