HOWTO » History » Revision 179
Revision 178 (David Galloway, 02/24/2021 06:43 PM) → Revision 179/187 (Loïc Dachary, 03/05/2021 07:08 AM)
h3. Introduction Backporting and the maintenance of a stable release begins when a new "stable Ceph release":https://docs.ceph.com/en/latest/releases/general/ release":http://ceph.com/docs/master/releases 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":https://docs.ceph.com/en/latest/releases/general/#stable-releases-x-2-z release":http://ceph.com/docs/master/releases is published. This repeats until the "the stable release is retired":https://docs.ceph.com/en/latest/releases/general/#lifetime-of-stable-releases. retired":http://ceph.com/docs/master/releases. Backporting is focused on fixing bugs and development on the master branch is expected to add new features. Both features but both share a "the same workflow":https://docs.ceph.com/en/latest/dev/developer_guide/basic-workflow/ with additional "tools and methods":https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst dedicated to help with backports. the "same workflow":http://ceph.com/docs/master/dev/development-workflow/. h3. Overview of the backports in progress * *octopus* ** "backports": http://tracker.ceph.com/projects/ceph/issues?query_id=199 ** "pending issues": http://tracker.ceph.com/projects/ceph/issues?query_id=215 ** "pull requests": https://github.com/ceph/ceph/milestone/13 * *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 h3. Leads * Ceph: Sage Weil * RADOS: Neha Ojha * RGW: Casey Bodley * CephFS: Patrick Donnelly * RBD: Jason Dillaman * Dashboard: Ernesto Puerta h3. Who's who Members of the "stable releases team":http://tracker.ceph.com/projects/ceph-releases are assigned the following roles as of March, 2021. September, 2017. | Name | IRC nick | | David Galloway | dgalloway | | Yuri Weinstein | yuriw | | Adam Kraitman | akraitman | | Loïc Dachary | loicd | h3. HOWTO The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases. h4. Add a new stable release * [[HOWTO start backporting a stable release]] h4. Add a new point release * [[HOWTO start working on a new point release]] h4. 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]] h4. Retire a stable release * [[HOWTO retire a stable release]] h4. Release management * [[HOWTO cut a release]] (DEPRECATED) * [[HOWTO announce a release]] (DEPRECATED. See https://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_write_the_release_notes#E-mail-Release-Notes) * [[HOWTO do dev checkpoint releases]] h4. Recurring duties expected from backporters * [[HOWTO triage incoming backport pull requests]] * [[HOWTO triage incoming Pending backport issues]] * "fill in the missing releases":http://tracker.ceph.com/projects/ceph/issues?query_id=84 h4. Organize the stable releases and backports team * [[HOWTO become a new team member]] * [[HOWTO retire from the team]]