Changes between Version 90 and Version 91 of ReleasePractices/ManagerCheckList
- Timestamp:
- Jan 22, 2015, 9:10:22 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReleasePractices/ManagerCheckList
v90 v91 10 10 * Update Trac milestones: https://svn.boost.org/trac/boost/admin/ticket/milestones 11 11 12 * In trunk, change version number in: 13 * trunk/index.html (2 places; H2 and Release History link) 14 * trunk/Jamroot (1 place) 15 * trunk/boost/version.hpp (2 places) - Note that `BOOST_LIB_VERSION` should not include the patch version if it's zero. 16 * trunk/more/getting_started/detail/release-variables.rst (4 places) 17 18 * In trunk, 19 * In more/getting_started, run`b2`. 12 * In boost super-project branch develop, change version number in: 13 * root/index.html (2 places; H2 and Release History link) 14 * root/Jamroot (1 place) 15 * root/boost/version.hpp (2 places) - Note that `BOOST_LIB_VERSION` should not include the patch version if it's zero. 16 * root/more/getting_started/detail/release-variables.rst (4 places) 17 * In root/more/getting_started, run`b2`. 20 18 * Inspect results. 21 19 22 20 * Commit version number and Getting Started doc changes: 23 * Commit trunk.24 * Merge to branches/release using merge_release_cycle_init.bat.25 * Commit to branches/release.21 * Commit develop, push. 22 * Merge develop to master. 23 * Commit master, push. 26 24 27 25 * Update the Google calendar as described in ReleaseSchedule so that it is always several releases ahead. '''This is really important; it causes endless trouble if the calendar isn't updated.'''