Changes between Version 6 and Version 7 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Jul 31, 2008, 8:10:29 PM (14 years ago)
Author:
Beman Dawes
Comment:

Update distribution instructions

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v6 v7  
    4141    * Monitor CVS commits to verify that all the expected and/or promised content actually gets committed. Try to get developers to avoid last minute commits of major changes.
    4242
    43 == Subversion Release ==
     43== Subversion Release Tag ==
    4444
    45     * Pre-release activities all complete?
    46        
    47     * Post notice to make sure all developers ready.
    48        
    49     * Tag: Version_x_yy_z. If prior release failed, select "overwrite existing tags with the same name".
     45    * Pre-release activities all complete?     
     46   
     47    * Create SVN release tag:
     48         * Copy (Branch/Tag)
     49         * From WC at URL: https://svn.boost.org/svn/boost/branches/release
     50         * To URL:         https://svn.boost.org/svn/boost/tags/release/Boost_#_##_#[_RC#|_beta#].
    5051
    5152== Distribution ==
    5253
    53      * Upload files for SourceForge release incoming directory using WS_FTP Pro
    54           * Start keep_isdn_awake
    55           * Connection: SourceForge Release Upload | connect
    56           * Select Local system: c:\boost
    57           * Select Remote system: /incoming
    58           * Drag-and-drop the three release files from Local system to Remote system
    59           * Disconnect
    60           * Stop keep_isdn_awake
    61              
    62     * Complete the SourceForge release procedure.
    63           * Admin | File Releases | Add Release for package name boost
    64           * New release name: 1.21.2 | create this release
     54     * See http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download for SourceForge File Release System documentation.
     55          * 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, just drag-and-drop the release file into it. Note: Hit F5 to see the correct file sizes after upload.
     56          * Create or edit a release. Admin | File Releases: Click "Add Release" for Package Name "boost".
     57          * New release name: 1.37.2 [beta] | create this release
    6558          * Step 1: paste in release notes (in HTML). Be sure to note difference between .zip and .gz/bz2 files. Submit/Refresh
    6659          * Step 2: Check appropriate files. Add Files and/or Refresh View
    67           * Step 3: For each file, select Processor and File Type, Update/Refresh
     60          * Step 3: For each file, select Processor "Platform-Independent" and File Type, Update/Refresh
    6861          * Setp 4: Email Release Notice: I'm sure. Send Notice.
    6962          * Wait up to 30 minutes.
    70           * Check SourceForge release page and release notes with web browser.
    71              
    72     * Consider putting up a temporary "Update in progress" root/index.html during site update
    73        
     63          * Check SourceForge release page and release notes with web browser.             
     64   
    7465    * Update the web site: TBS
    7566