Changes between Version 10 and Version 11 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Aug 13, 2008, 12:41:51 PM (14 years ago)
Author:
Beman Dawes
Comment:

Add final review step before SourceForge distribution

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v10 v11  
    33= Release Manager's Checklist =
    44
    5 ''This is being rewritten to the current Boost release precess.''
     5''This page is gradually being rewritten to reflect the current Boost release process. Until the rewrite is complete, some sections are out-of-date''
    66
    77== Introduction ==
    … …  
    5555         * Create copy in the repository from: Head revision in the repository
    5656
     57== Build Distribution packages ==
     58
     59    * Build the distribution packages using tools/release/???.sh.
     60
     61    * Upload distribution packages to snapshot ftp site.
     62
     63    * '''''Important''''': Request final review from release team, developers list. 
     64
    5765== Distribution ==
    5866
    59      * See http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download for SourceForge File Release System documentation.
     67    * '''''Important''''': Release team must have signed off on packages. Ignoring this in the past has led to mistakes!
     68 
     69    * See http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download for SourceForge File Release System documentation.
    6070
    61      * Upload release files. WebDAV works well; use URL https://frs.sourceforge.net/b/be/beman_dawes/uploads/. The user id and password may have to be entered twice. Once the uploads directory window opens, use '''Windows Explorer''' as a drag-and-drop target. Note: Hit F5 to see the correct file sizes after upload.
     71    * Upload release packages. WebDAV works well; use URL https://frs.sourceforge.net/b/be/beman_dawes/uploads/. The user id and password may have to be entered twice. Once the uploads directory window opens, use '''Windows Explorer''' as a drag-and-drop target. Note: Hit F5 to see the correct file sizes after upload.
    6272
    63      * Create or edit a release. Admin | File Releases: Click "Add Release" for Package Name "boost".
     73    * Create or edit a release. Admin | File Releases: Click "Add Release" for Package Name "boost".
    6474 
    6575          * Step 1: New release name: 1.37.2 [beta] | create this release
    … …  
    7484          * Step 5: Email Release Notice: Check "I'm sure", click "Send Notice"
    7585
    76     * Wait a bit. The docs say 30 minutes, but that seems to have been reduced to less than 5 minutes.
    77     * Check SourceForge release page and release notes with web browser.             
     86   * Wait a bit. The docs say 30 minutes, but that seems to have been reduced to less than 5 minutes.
     87   * Check SourceForge release page and release notes with web browser.             
    7888   
    79     * Update the web site: TBS
     89   * Update the web site: TBS
    8090
    81     * Check actual www.boost.org site with browser. Look at a bunch of files that should have been updated to make sure the updates actually "took".
     91   * Check actual www.boost.org site with browser. Look at a bunch of files that should have been updated to make sure the updates actually "took".
    8292       
    83     * 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       
     93   * 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       
    8494
    85     * 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).
     95   * 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).
    8696
    87     * Merge version number changes to branches/release.
     97   * Merge version number changes to branches/release.
    8898       
    8999----