HOWTO start backporting a stable release » History » Revision 8
Revision 7 (Loïc Dachary, 08/15/2015 10:23 AM) → Revision 8/11 (Loïc Dachary, 08/29/2015 12:53 PM)
h3. Introduction When backporting starts, a branch named after the release (for instance "firefly":https://ceph.com/git/?p=ceph.git;a=shortlog;h=refs/heads/firefly) already exists. h3. Add a new release in redmine * http://tracker.ceph.com/rb/release/ceph/new * the name of the release is the name of the ceph release, with the first letter uppercase (Firefly, Hammer ...) * the start date is the month when the stable release branch was created first published * the end date is the documented "estimated retirement":http://ceph.com/docs/master/releases/ * Update the [[HOWTO|HOWTO landing page]] * Update the "project overview":http://tracker.ceph.com/projects/ceph-releases/settings/info h3. Add a new integration branch in git For instance "firefly-backports":https://ceph.com/git/?p=ceph.git;a=shortlog;h=refs/heads/firefly-backports * release=firefly * git checkout -b $release-backports $release * git push ceph $release-backports h3. Update websites with the new release * ceph.com : http://ceph.com/resources/downloads/ * wikipedia : https://en.wikipedia.org/wiki/Ceph_%28storage%29