Backporting and the maintenance of a stable release begins when a new stable Ceph release is published. Commits from the master branch are cherry-picked to the stable branch and run through integration and upgrade tests. After a few weeks a point release is published. This repeats until the the stable release is retired. Backporting is focused on fixing bugs and development on the master branch is expected to add new features. Both share a the same workflow with additional tools and methods dedicated to help with backports.

Overview of the backports in progress

Who's who

Members of the stable releases team as of March, 2021.

Name IRC nick
David Galloway dgalloway
Yuri Weinstein yuriw
Adam Kraitman akraitman
Nathan Cutler smithfarm
Loïc Dachary loicd


The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases.

Add a new stable release

Add a new point release

Prepare a new point release

  1. HOWTO monitor the automated tests AKA nightlies
  2. HOWTO schedule an issue for backporting
  3. HOWTO document user visible changes
  4. HOWTO backport commits
  5. HOWTO populate the integration branch
  6. HOWTO run integration and upgrade tests
  7. HOWTO forensic analysis of integration and upgrade tests
  8. HOWTO describe a test result
  9. HOWTO merge commits from the integration branch
  10. HOWTO synchronize pull requests from different repositories
  11. HOWTO resolve issues that are Pending Backport
  12. HOWTO get the Ceph lead to decide if it is time for a point release
  13. HOWTO get the leads to sign-off on a release
  14. HOWTO write the release notes
  15. HOWTO keep backporting while the release branch is frozen

Retire a stable release

Release management

Recurring duties expected from backporters

Organize the stable releases and backports team

Updated by Loïc Dachary almost 3 years ago · 187 revisions