Changes between Version 12 and Version 13 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Aug 18, 2008, 8:06:31 PM (14 years ago)
Author:
Beman Dawes
Comment:

Start work on Release cycle initialization

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v12 v13  
    77== Introduction ==
    88
    9 Historically, items on this checklist were accomplished by scripts written in Perl, Python, Bash, C++, and as Windows command files, or by point-and-click on a FrontPage or other GUI based program. Long term the plan is to move as much as possible of these to C++, as the one language all Boost developers are comfortable with.
    109
    11 == Pre-release activities ==
     10== Release cycle initialization ==
    1211
    13     * After discussion on the main list, post the release schedule.
     12   * Request that the new version number is added to Trac.
     13
     14   * Ready trunk/index.html, trunk/boost/version.hpp, and trunk/Jamroot, trunk/more/getting_started/detail/release-variables.rst for the next release and commit to Subversion. (Possibly also update trunk/more/getting_started/unix-variants.rst, and also work rebuilding the getting started guide into the process somewhere).
     15
     16   * Merge version number changes to branches/release.
     17
     18    * Update ReleaseSchedule
     19
     20    * Post the "Release open for merges" message. See ???
    1421       
    1522    * Verify the root/index.htm, root/boost/version.hpp, root/Jamfile.v2 and root/Jamrules release numbers are correct and agree.
    … …  
    93100       
    94101   * 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       
    95 
    96    * Request that the new version number is added to Trac.
    97 
    98    * Ready trunk/index.html, trunk/boost/version.hpp, and trunk/Jamroot, trunk/more/getting_started/detail/release-variables.rst for the next release and commit to Subversion. (Possibly also update trunk/more/getting_started/unix-variants.rst, and also work rebuilding the getting started guide into the process somewhere).
    99 
    100    * Merge version number changes to branches/release.
    101        
     102     
    102103----
    103104Copyright Beman Dawes 2001, 2008