Changes between Version 29 and Version 30 of ReleasePractices/ManagerCheckList

Timestamp:

Feb 11, 2009, 12:19:19 PM (14 years ago)

Author:

Beman Dawes

Comment:

Add New Library Checklist section

ReleasePractices/ManagerCheckList

@@ -41 +41 @@
        Then edit the new entry and commit.
        
-    * For each new library added this release:
-        * Verify root/index.html includes the library in it's new library list.
-        * Verify root/libs/libraries.htm entry has been made, both in the alphabetic list and in the category lists.
-        * Verify root/libs/maintainers.txt entry has been made.
-        * Verify website/public_html/beta/feed/history/ entry has been made and reads well.
-        * Verify library has been added to the website documentation list
-        * Verify the root/libs/xxx directory contains an index.htm or index.html file; either the main docs or a redirection to the main docs. To do: automate this.
-        * Skim read the primary docs pages to make sure they meet Boost requirements and guidelines. Don't leave this until too late; it has turned up lots of issues in the past.
-        * Generate the header dependency table and update the CVS. To do: coordinate with John Maddock's new dependency tools.
-        * Add to component list on Trac (this could possibly be done when the library is accepted, or even added to the review queue).
-
     * Monitor http://boost.sourceforge.net/regression-logs/inspection_report.html to verify problems are actively being reduced. Make sure none of the problems are in files the release manager is responsible for.
        
@@ -64 +53 @@
        
     * Monitor SVN 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.
+
+== New Library Checklist ==
+
+Before a new library is merged into branches/release, the release manager should verify:
+
+    * root/index.html includes the library in it's list of new libraries.
+    * root/libs/libraries.htm entry is OK, both in the alphabetic list and in the category lists.
+    * root/libs/maintainers.txt entry is OK.
+    * website/public_html/beta/feed/history/ entry is OK.
+    * The library has been added to the website documentation list
+    * The library's root/libs/xxx directory contains an index.htm or index.html file with either the main docs or a redirection to the main docs.
+    * The primary docs pages meet Boost requirements and guidelines. Don't leave this until too late; it has turned up lots of issues in the past.
+    * Add to component list on Trac (this could possibly be done when the library is accepted, or even added to the review queue).
+    * Trunk inspection report is clean.
+    * Trunk regression tests are reasonably clean or marked up.
+
+After a new library is merged into branches/release, the release manager should verify: 
+
+    * Doc builds, if any, are running properly.
+    * Release branch inspection report is clean.
+    * Release branch regression tests are reasonably clean or marked up.
 
 == Beta Release ==