Changes between Version 100 and Version 101 of ReleasePractices/ManagerCheckList

Timestamp:

Apr 15, 2018, 7:59:20 PM (5 years ago)

Author:

Daniel James

Comment:

--

ReleasePractices/ManagerCheckList

@@ -140 +140 @@
 == Build Distribution Packages ==
 
-    * Make sure that the documentation is up to date. In particular, when the documentation source files get updated, the docs for the website need to be regenerated and merged to release.
-
-    * If it hasn't already been done, run a snapshot using tools/release/snapshot.bat.
-    
-    * Build the distribution packages using tools/release/build_release_packages.bat.
-{{{
-cd <snapshot-directory>
-%BOOST_TRUNK%\tools\release\build_release_packages boost_X_XX_X_beta1 >build_packages.log 2>&1
-}}} 
-
-    * Unpack the distribution package for your local operating system, and verify build works OK. No point in posting a release candidate already known to fail!
-{{{
-cd <boost-root>
-bootstrap
-.\b2 >build.log 2>&1
-}}}    
-
-    * Upload distribution packages to snapshot ftp site.
+    * Up to date instructions on [https://github.com/boostorg/boost/wiki/Preparing-Releases GitHub wiki].
 
     * '''''Important''''': Post request for review of release candidates. See [wiki:ReleasePractices/HeadsUpMessages#n.nn.nReleasecandidatesavailable sample candidates avaiable notice]. 
@@ -164 +147 @@
 
     * '''''Important''''': Release team must have signed off on packages. Ignoring this in the past has led to mistakes!
+
+    * Instructions for uploading to bintray on [https://github.com/boostorg/boost/wiki/Preparing-Releases GitHub wiki].
   
     * See http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download for SourceForge File Release System (RFS) documentation.