Changes between Version 85 and Version 86 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Nov 9, 2014, 11:13:49 PM (8 years ago)
Author:
Daniel James
Comment:

Instructions for tagging the version in git.

Legend:

Unmodified
Added
Removed
Modified
  • ReleasePractices/ManagerCheckList

    v85 v86  
    160160        * Go back to this release's folder, and click on the 'i' icon to the right of the 'tar.bz2' file, select 'default download' for everything but windows, and click on 'save'. Once that has finished (it can be slow, you might want to open the page in another window), click on the 'i' icon to the right of the 'zip' file and select windows, and click on 'save' again.
    161161
    162    * Apply Subversion release tag. (See [#SubversionReleaseTag Subversion Release Tag])
     162   * Tag the release in git. Make sure the correct versions of the super project and submodules are checked out, and then do something like:
     163     {{{
     164     git tag boost-1.58.0
     165     git submodule foreach 'git tag boost-1.58.0'
     166     git push origin boost-1.58.0
     167     git submodule foreach 'git push origin boost-1.58.0'
     168     }}}
    163169
    164170   * If this is a final release, rather than a beta release, let the webmaster (currently Daniel) know the release is ready to go live. Wait until the site is updated before posting the release message.
     
    167173       * Beta releases: See [wiki:ReleasePractices/HeadsUpMessages#Boostn.nn.nBetanReleaseNotice sample beta release notice].  Post as separate messages to: boost, boost-announce, boost-users
    168174       * Final releases: See [wiki:ReleasePractices/HeadsUpMessages#Boostn.nn.nReleaseNotice sample final release notice].  Post as separate messages to: boost, boost-announce, boost-users, comp.lang.c++.moderated, c++std-news       
    169      
    170 == Subversion Beta and Release Tags ==
    171 
    172 Obtain the revision number from the end of build_packages.log
    173 
    174 With TortoiseSVN:
    175  
    176    * Select the revision number for the release; right-click and select "Create branch/tag from revision".
    177        * To path: /tags/release/Boost_1_50_0_beta1, resulting in a Destination URL: https://svn.boost.org/svn/boost/tags/release/Boost_n_nn_n_beta1
    178        * Specific revision in repository: should already be set to correct revision number.
    179        * '''Log message: Release n.n.n beta 1'''
    180        * Click OK     
    181 
    182 With a command-line tool (where XXXXX is the revision that you want to branch from)
    183    * svn cp https://svn.boost.org/svn/boost/branches/release@XXXXX \
    184        https://svn.boost.org/svn/boost/tags/release/Boost_n_nn_n_beta1 -m "Release n.n.n beta 1"
    185 
    186    
     175 
    187176----
    188177Copyright Beman Dawes 2001, 2008