HOWTO start backporting a stable release » History » Revision 2
Revision 1 (Loïc Dachary, 03/26/2015 10:06 AM) → Revision 2/11 (Loïc Dachary, 03/26/2015 10:11 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-releases/new * the name of the release is the name of the ceph release, all lowercase * the start date is the month when the stable release was first published * the end date is six months after the documented "lifetime expectancy":http://ceph.com/docs/master/releases/ because that is more or less what happens in practice http://tracker.ceph.com/rb/releases/ceph-releases 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