HOWTO » History » Revision 34
« Previous |
Revision 34/187
(diff)
| Next »
Loïc Dachary, 04/09/2015 01:44 PM
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¶
Add a new point release¶
Prepare a new point release¶
- HOWTO schedule an issue for backporting
- HOWTO update the inventory
- HOWTO document user visible changes
- HOWTO backport commits
- HOWTO populate the integration branch
- HOWTO run integration and upgrade tests
- HOWTO describe a test result inline or HOWTO summarize test results in a separate issue
- HOWTO merge commits from the integration branch
- HOWTO synchronize pull requests from different repositories
- HOWTO resolve issues that are Pending Backport
- HOWTO get the Ceph lead to decide if it is time for a point release
- HOWTO get the leads to sign-off on a release
- HOWTO write the release notes
Retire a stable release¶
Updated by Loïc Dachary about 9 years ago · 34 revisions