Skip to content

Releases: Checklists

Jump to bottom
Marshall Clow edited this page Dec 8, 2021 · 6 revisions

Release Manager Checklists

Release cycle initialization

  • Update Trac milestones: https://svn.boost.org/trac/boost/admin/ticket/milestones

  • In boost super-project branch develop, change version number in:

    • root/Jamroot (1 place)
    • root/CMakeLists.txt (1 place)

  • In more branch, change version number in:

    • root/getting_started/detail/release-variables.rst (4 places)
    • In root/getting_started, run b2.
    • Inspect results.

  • Commit version number and Getting Started doc changes:

    • Commit develop, push.
    • Cherry-pick develop to master.
    • Commit master, push.

  • Create a pull request for config:

    • include/boost/version.hpp (2 places) - Note that BOOST_LIB_VERSION should not include the patch version if it's zero.

  • Verify the root/index.html, root/boost/version.hpp, root/Jamroot release numbers are correct and agree.

  • Create a placeholder for release information at: website/public_html/live/feed/history/, for example for boost 1.60.0:

git clone git@github.com:boostorg/website.git live-website
cd live-website
cp feed/templates/boost_x_xx_x.qbk feed/history/boost_1_60_0.qbk
  • Edit the version number, at the top,in the new entry. Then..
git add feed/history/boost_1_60_0.qbk
git commit -a -m "Stub release notes for 1.60.0"
git push
  • 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.

There's a tool in release-tools that generates a year's worth of CSV that can be imported into Google Calendar:

generate_boost_calendar.py -y 2022 -r 79
  • Post the "Open for merges" heads up message. See Heads up messages to notify developers as deadlines loom

logo

Clone this wiki locally