HOWTO start backporting a stable release » History » Revision 6
Revision 5 (Loïc Dachary, 04/13/2015 12:57 PM) → Revision 6/11 (Loïc Dachary, 05/22/2015 08:49 AM)
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 http://tracker.ceph.com/rb/release/ceph-releases/new * the name of the release is the name of the ceph release, with the first letter uppercase (Firefly, Hammer ...) all lowercase * the start date is the month when the stable release was first published * the end date is six months after the documented "estimated retirement":http://ceph.com/docs/master/releases/ "lifetime expectancy":http://ceph.com/docs/master/releases/ because that is more or less what happens in practice * 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. Create a new version * Add something like *v0.94.1* *hammer v0.94.1* in http://tracker.ceph.com/projects/ceph/settings/versions http://tracker.ceph.com/projects/ceph-releases/settings/versions * Create a new issue to track the progress, copying an existing one (for instance http://tracker.ceph.com/issues/11353) * Update the [[HOWTO|HOWTO landing page]] h3. Update websites with the new release * ceph.com : http://ceph.com/resources/downloads/ * wikipedia : https://en.wikipedia.org/wiki/Ceph_%28storage%29