Changes between Version 4 and Version 5 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Jul 2, 2008, 5:58:49 PM (14 years ago)
Author:
Daniel James
Comment:

Some maintance tasks related to website. Probably not the release managers responsibility, but might be worth including in the list (or separating into a new list)

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v4 v5  
    1717    * Verify via jamboost@yahoogroups.com that bjam pre-built executables up-to-date.
    1818       
    19     * Remove the oldest "Latest News" from root/index.htm.
     19    * Create a placeholder for release information at: website/public_html/beta/feed/history/
    2020       
    2121    * For each new library added this release:
    22         * Verify root/index.htm Latest News entry has been made and reads well.
     22        * Verify website/public_html/beta/feed/history/ entry has been made and reads well.
    2323        * Verify root/libs/libraries.htm entry has been made, both in the alphabetic list and in the category lists.
     24        * Verify root/libs/maintainers.txt entry has been made.
     25        * Verify library has been added to the website documentation list
    2426        * 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.
    2527        * 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.