Changes between Version 11 and Version 12 of ReleasePractices/ManagerCheckList


Ignore:
Timestamp:
Aug 15, 2008, 8:02:03 AM (14 years ago)
Author:
Daniel James
Comment:

Also need to add release details to Trac.

Legend:

Unmodified
Added
Removed
Modified

  • ReleasePractices/ManagerCheckList

    v11 v12  
    2727        * 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.
    2828        * Generate the header dependency table and update the CVS. To do: coordinate with John Maddock's new dependency tools.
     29        * Add to component list on Trac (this could possibly be done when the library is accepted, or even added to the review queue).
    2930
    3031    * 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.
    … …  
    9394   * Post a message announcing the release and recapping "Latest News".  Post as separate messages to: boost, boost-announce, boost-users, comp.lang.c++.moderated, c++std-news       
    9495
     96   * Request that the new version number is added to Trac.
     97
    9598   * Ready trunk/index.html, trunk/boost/version.hpp, and trunk/Jamroot, trunk/more/getting_started/detail/release-variables.rst for the next release and commit to Subversion. (Possibly also update trunk/more/getting_started/unix-variants.rst, and also work rebuilding the getting started guide into the process somewhere).
    9699