Changes between Version 42 and Version 43 of ReleasePractices/ManagerCheckList

Timestamp:

Nov 4, 2009, 1:16:59 PM (13 years ago)

Author:

Beman Dawes

Comment:

Update release instructions for SourceForge

ReleasePractices/ManagerCheckList

@@ -108 +108 @@
         * login
         * Project Admin | File Manager
-        * Right click "boost" | New folder 
+        * Right click "boost" | New folder | New folder name: 1.41.0.beta.1 
 
-    * Upload release packages to folder just created.
+    * Upload release packages:
 {{{
 cd <snapshot-directory>
 dir boost_*              // verify this gets only the desired files
-%BOOST_TRUNK%\tools\release\upload2sourceforge boost.1.40.0.beta.2
+%BOOST_TRUNK%\tools\release\upload2sourceforge 1.41.0.beta.1
 }}}
 
-   * Wait a bit. The docs say 30 minutes, but that seems to have been reduced to less than 5 minutes.
+   * Complete SourceForge release process:
+        * login
+        * Project Admin | File Manager
+        * Verify files are present and in the correct directory.
+        * Click each file to set properties:
+            * Label: "Windows line endings" or "Unix line endings"
+            * Do not set Platform, since we have no default download platform.
+        * Files (on upper menu bar), and check "Newest Files" entries are correct. (There may be a delay before labels appear)
 
    * Apply Subversion release tag. (See [#SubversionReleaseTag Subversion Release Tag])
 
-   * Check SourceForge release page and release notes with web browser.             
-   
    * Upload boost_n_n_n.zip to the web server (Requires server keys/access; currently only Rene and Beman. Also assumes ~/.ssh has Beman's key files):
 {{{