HOWTO » History » Revision 170
« Previous |
Revision 170/187
(diff)
| Next »
Nathan Cutler, 07/22/2019 02:59 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 the stable release is retired. 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¶
- nautilus
- "backports": http://tracker.ceph.com/projects/ceph/issues?query_id=171
- "pending issues": http://tracker.ceph.com/projects/ceph/issues?query_id=172
- "pull requests": https://github.com/ceph/ceph/milestone/12
- mimic
- "backports": http://tracker.ceph.com/projects/ceph/issues?query_id=150
- "pending issues": http://tracker.ceph.com/projects/ceph/issues?query_id=151
- "pull requests": https://github.com/ceph/ceph/milestone/11
- luminous
- "backports": http://tracker.ceph.com/projects/ceph/issues?query_id=127
- "pending issues": http://tracker.ceph.com/projects/ceph/issues?query_id=128
- "pull requests": https://github.com/ceph/ceph/milestone/10
Leads¶
- Ceph : Sage Weil
- rados : Josh Durgin
- radosgw / rgw : Yehuda Sadeh
- CephFS / fs : Patrick Donnelly
- RBD : Jason Dillaman
Note: It may be useful to know the leads of other projects which have a different lifecycle but depend on Ceph.
Who's who¶
Members of the stable releases team are assigned the following roles as of September, 2017.
Name | IRC nick |
Abhishek Lekshmanan | theanalyst |
Yuri Weinstein | yuriw |
Nathan Cutler | smithfarm |
TBA | TBA |
- Mentee: during the course of a release the driver is available to help understand the stable release workflow
- Driver: responsible for making sure the release is moving forward
- Backup: helps the driver and replaces her/him when she/he is not available
- Sage Weil, Patrick Donnelly, Jason Dillaman, Josh Durgin, Yehuda Sadeh: leads
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 monitor the automated tests AKA nightlies
- HOWTO schedule an issue for backporting
- HOWTO document user visible changes
- HOWTO backport commits
- HOWTO review backport PRs
- HOWTO populate the integration branch
- HOWTO run integration and upgrade tests
- HOWTO forensic analysis of integration and upgrade tests
- HOWTO describe a test result
- 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
- HOWTO keep backporting while the release branch is frozen
Publish a release¶
Retire a stable release¶
Release management¶
Recurring duties expected from backporters¶
- HOWTO triage incoming backport pull requests
- HOWTO triage incoming Pending backport issues
- fill in the missing releases
Organize the stable releases and backports team¶
Updated by Nathan Cutler almost 5 years ago · 170 revisions