HOWTO » History » Revision 22
Revision 21 (Loïc Dachary, 03/26/2015 10:51 AM) → Revision 22/187 (Loïc Dachary, 03/26/2015 11:05 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/.
The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases.
h3. Add a new stable release
* [[HOWTO start backporting a stable release]]
h3. Add a new point release
* [[HOWTO start working on a new point release]]
h3. 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 synchronize pull requests from different repositories]]
h3. Retire a stable release
* [[HOWTO retire a stable release]]