HOWTO » History » Revision 153
Revision 152 (Loïc Dachary, 10/03/2016 01:42 PM) → Revision 153/187 (Abhishek Lekshmanan, 10/05/2016 07:49 AM)
h3. Introduction Backporting and the maintenance of a stable release begins when a new "stable Ceph 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":http://ceph.com/docs/master/releases is published. This repeats until the "the stable release is 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 but both share the "same workflow":http://ceph.com/docs/master/dev/development-workflow/. h3. Overview of the backports in progress * *jewel* ** "complete":http://tracker.ceph.com/versions/524 ** "backport status":http://tracker.ceph.com/issues/17487 ** "backports":http://tracker.ceph.com/projects/ceph/issues?query_id=96 ** "pending issues":http://tracker.ceph.com/projects/ceph/issues?query_id=97 ** "pull requests":https://github.com/ceph/ceph/milestone/8 * *hammer* ** "complete":http://tracker.ceph.com/versions/525 ** "backport status":http://tracker.ceph.com/issues/15895 ** "backports":http://tracker.ceph.com/projects/ceph/issues?query_id=78 ** "pending issues":http://tracker.ceph.com/projects/ceph/issues?query_id=77 ** "pull requests":https://github.com/ceph/ceph/milestone/5 h3. Leads * Ceph : Sage Weil * rados : Samuel Just * radosgw / rgw : Yehuda Sadeh * CephFS / fs : John Spray * RBD : Jason Dillaman * build/ops : Ken Dreyer Note: It may be useful to know the leads of other projects which have a different lifecycle but depend on Ceph. h3. Who's who Members of the "stable releases team":http://tracker.ceph.com/projects/ceph-releases are assigned the following roles as of August, 2016. | Name | IRC nick | v0.94.10 | v10.2.4 | | Abhishek Lekshmanan | theanalyst | | backup | | Abhishek Varshney | abhishekvrshny | | driver | | Nathan Cutler | smithfarm | driver | | | Loic Dachary | loicd | backup | backup | * 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, Samuel Just, Yehuda Sadeh, John Spray, Jason Dillaman: leads 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 formally announce release]] h4. Publish a release * [[HOWTO publish a release]] h4. Retire a stable release * [[HOWTO retire a stable release]] 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]]