Changes between Version 96 and Version 97 of ReleasePractices/ManagerCheckList

Timestamp:

Jun 7, 2016, 7:21:34 PM (6 years ago)

Author:

Daniel James

Comment:

Update instructions - maintainers.txt and libraries.htm are automatically updated. We're not creating teams any more.

ReleasePractices/ManagerCheckList

@@ -78 +78 @@
         * If the library already has a !GitHub repository, [https://help.github.com/articles/transferring-a-repository/ transfer the repository to boostorg]. Getting the maintainer to transfer into the organization is a bit awkward. So it might be best to first transfer the repo to an admin, who can then transfer it into the organization and set up the team.
         * If the library does not already have a !GitHub repository, [https://github.com/organizations/boostorg/repositories/new Create the library's repository]. Note: the release manager creates a repository 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].
+    * Go into the repo settings, and make sure the owner has admin permissions.
 
 === Add library as a submodule on boost develop branch ===
@@ -96 +96 @@
 
     * The formal review manager is satisfied any requirements for inclusion set by the formal review have been met.
-    * `root/libs/libraries.htm` entry is OK, both in the alphabetic list and in the category lists.
-    * `root/libs/maintainers.txt` entry is OK.
     * The repo contains an `index.html` file with either the main docs or a redirection to the main docs.
     * [http://www.boost.org/development/library_metadata.html `meta/libraries.json`] is present in the repo and contents look reasonable.