Changes between Version 86 and Version 87 of ReleasePractices/ManagerCheckList

Timestamp:

Jan 22, 2015, 2:40:50 PM (8 years ago)

Author:

Beman Dawes

Comment:

Update New lib checklist for Git

ReleasePractices/ManagerCheckList

@@ -1 +1 @@
 [[PageOutline]]
 
-= Release Manager's Checklist =
+= Release Manager Checklists =
 
 == Introduction ==
@@ -57 +57 @@
 == New Library Checklist ==
 
-Before a new library is merged into branches/release, the release manager should verify:
+=== Create !GitHub Repository
+
+Before a release manager creates a [https://github.com/boostorg boostorg GitHub] repository for the new library, the release manager should send an email to 
+developer:
+
+    * Ask the developer to read this checklist (i.e. https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList#NewLibraryChecklist) so that he or she will be aware of the steps that will have to be completed to add a library to the Boost distributions.
+    * Ask for the GitHub user-id of the developer and anyone else to be given read-write access to the library's repository.
+
+The release manager performs two steps to add the new library to [https://github.com/boostorg GitHub]:
+
+    * [https://github.com/orgs/boostorg/new-team Create the library's repository]. Note: the release manager creates a repo that is empty except for a readme file. The library's developer is responsible for creating the library's contents.
+    * [https://github.com/orgs/boostorg/new-team Create a team for the library].
+
+=== Add library as a submodule on boost develop branch ===
+
+Before a release manager adds the library as a submodule on the boost super-project develop branch, the release manager should verify the library is ready to start regression testing:
+
+    * The critical elements of the library xxx directory structure are in place:
+        * libs/xxx/include/boost/xxx has the header files.
+        * libs/xxx/test has a Jamfile.v2, and {{{b2}}} works. Tests don't have to pass, but the Jamfile needs to be in good enough shape that it will not break regression testing.
+        * If it is a compiled library, libs/xxx/build has a Jamfile.v2 in in good enough shape that it will not break regression testing.
+        * The directory structure in general is reasonably complete and boost-like.
+    * Run inspect and verify the report is not a total disaster. It does not have to be totally clean, but it should be clean enough to indicate the developer has the general idea of what is required.
+
+=== Add library as a submodule on boost master branch ===
+
+Before a release manager adds the library as a submodule on the boost super-project master branch, the release manager should verify:
 
     * root/libs/libraries.htm entry is OK, both in the alphabetic list and in the category lists.
@@ -63 +89 @@
     * The library's root/libs/xxx directory contains an 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.
-    * 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: 
+    * Inspection report is clean.
+    * Regression on develop tests are reasonably clean.
+
+After a new library is merged into master, the release manager should verify: 
 
     * Doc builds, if any, are running properly.