HOWTO » History » Revision 27
Revision 26 (Loïc Dachary, 03/26/2015 11:51 AM) → Revision 27/187 (Loïc Dachary, 03/26/2015 11:58 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 "lifetime of the stable release":http://ceph.com/docs/master/releases 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":http://ceph.com/docs/master/dev/development-workflow/. h3. Overview of the backports in progress * "Giant":http://tracker.ceph.com/issues/11153 * "Firefly":http://tracker.ceph.com/issues/11090 * "Dumpling":http://tracker.ceph.com/issues/10560 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 schedule an issue for backporting]] # [[HOWTO update the inventory]] # [[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 update issues that are Pending Backport]] h4. Retire a stable release * [[HOWTO retire a stable release]]