Preparation for New Pacemaker Release Series

Updated 10 Days AgoPublic

Actions

Update project manager

• Create the milestone for the first release of the new series.
• Clone T1 for the new series, and decide which platform and dependency versions will be raised.
• Create tasks (or add series tag to existing tasks) to make any changes made possible by the new dependency versions.
• Create task to update the Clusters from Scratch document once the new series is available in the OS used for examples.
• Update any desired tasks from Future Release Series to add the series tag, raise priority, and assign, as appropriate.

Notify the community

• Create changes page(s) for the new series on this wiki under Pacemaker (see existing examples).
• Email users@clusterlabs.org with the changes page link and expected release schedule.

Create and merge PR

• Update INSTALL.md for the new dependency versions.
• Update the supported series in CONTRIBUTING.md and SECURITY.md.
• For a new major series, update Pacemaker Explained to remove any "(since <version>)" for older versions no longer supported in rolling upgrades.
• Run cts/cts-scheduler --update (only if the tests already all pass!) to update whitespace usage in expected output (which is ignored by regression tests, but can help manual comparisons)

Other

• Create the release branch from the current main branch.
• Ensure CI gets updated to check the main and new series branches only on platforms with the new dependency versions.
• Create, merge, and deploy a PR for the clusterlabs-www repo to add build-$SERIES.txt and title-$SERIES.txt in src/static/projects/pacemaker/doc/ (see existing examples)