Actions
HOWTO start backporting a stable release » History » Revision 3
« Previous |
Revision 3/11
(diff)
| Next »
Loïc Dachary, 04/09/2015 03:46 PM
Introduction¶
When backporting starts, a branch named after the release (for instance firefly) already exists.
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 because that is more or less what happens in practice
- Update the HOWTO landing page
- Update the project overview
Add a new integration branch in git¶
For instance firefly-backports
- release=firefly
- git checkout -b $release-backports $release
- git push ceph $release-backports
Create a new version¶
- Add something like hammer v0.94.1 in 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 landing page
Updated by Loïc Dachary about 9 years ago · 3 revisions