Ceph » Stable releases

Introduction¶

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 lifetime of the stable release comes to an end. Backporting is focused on fixing bugs and development on the master branch is expected to add new features but both share the same workflow.

Overview of the backports in progress¶

• no hammer backport status yet and all issues marked hammer
• giant backport status and all issues marked giant
• firefly backport status and all issues marked firefly
• dumpling backport status and no more issues marked dumpling

Leads¶

• rados : Samuel Just
• radosgw / rgw : Yehuda Sadeh
• CephFS / fs : Gregory Farnum
• RBD : Josh Durgin

HOWTO¶

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

Add a new stable release¶

• HOWTO start backporting a stable release

Add a new point release¶

• HOWTO start working on a new point release

Prepare a new point release¶

1. HOWTO schedule an issue for backporting
2. HOWTO update the inventory
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 describe a test result inline or HOWTO summarize test results in a separate issue
8. HOWTO merge commits from the integration branch
9. HOWTO synchronize pull requests from different repositories
10. HOWTO resolve issues that are Pending Backport
11. HOWTO get the leads to sign-off on a release
12. HOWTO write the release notes

Retire a stable release¶

• HOWTO retire a stable release