Changes between Version 87 and Version 88 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Jan 22, 2015, 2:48:43 PM (8 years ago)
Author:
Beman Dawes
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v87 v88  
    6363
    6464    * 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.
    65     * Ask for the GitHub user-id of the developer and anyone else to be given read-write access to the library's repository.
     65    * Ask for the !GitHub user-id of the developer and anyone else to be given read-write access to the library's repository.
    6666
    6767The release manager performs two steps to add the new library to [https://github.com/boostorg GitHub]:
    … …  
    8787    * root/libs/libraries.htm entry is OK, both in the alphabetic list and in the category lists.
    8888    * root/libs/maintainers.txt entry is OK.
    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.
     89    * root/libs/xxx contains an index.html file with either the main docs or a redirection to the main docs.
     90    * root/libs/meta/libraries.json is present and contents look reasonable.
    9091    * 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.
    9192    * Inspection report is clean.