Changes between Version 18 and Version 19 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Nov 3, 2008, 12:47:24 PM (14 years ago)
Author:
Beman Dawes
Comment:

Move Subversion Release Tag

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v18 v19  
    6767See ReleasePractices/PostBetaMerges
    6868
    69 == Subversion Release Tag ==
    70 
    71     * Do a local working copy Update to verify no past-deadline changes were made (and thus escaped testing).
    72 
    73     * Do a last review of the regression test results to verify no unexpected failures occurred.
    74 
    75     * Check developer's list to verify no last minute showstoppers were reported.     
    76    
    77     * Create SVN release tag:
    78          * Copy (Branch/Tag)
    79          * From WC at URL: https://svn.boost.org/svn/boost/branches/release
    80          * To URL:         https://svn.boost.org/svn/boost/tags/release/Boost_#_##_#[_RC#|_beta#].
    81          * Create copy in the repository from: Head revision in the repository
    82 
    8369== Build Distribution packages ==
    8470
    … …  
    121107   * Post a message announcing the release and recapping "Latest News".  Post as separate messages to: boost, boost-announce, boost-users, comp.lang.c++.moderated, c++std-news       
    122108     
     109== Subversion Release Tag ==
     110
     111With TortoiseSVN:
     112 
     113   * Do a log on an updated local working copy of branches/release.
     114
     115   * Select the revision number for the release; right-click and select "Create branch/tag from revision".
     116       * To URL: https://svn.boost.org/svn/boost/tags/release/Boost_n_nn_n
     117       * Specific revision in repository: should already be set to correct revision number.
     118       * Log message: Release 1.37.0
     119       * Click OK     
     120   
    123121----
    124122Copyright Beman Dawes 2001, 2008