Actions
HOWTO start backporting a stable release » History » Revision 6
« Previous |
Revision 6/11
(diff)
| Next »
Loïc Dachary, 05/22/2015 08:49 AM
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/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 was first published
- the end date is the documented estimated retirement
- 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 v0.94.1 in http://tracker.ceph.com/projects/ceph/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
Update websites with the new release¶
- ceph.com : http://ceph.com/resources/downloads/
- wikipedia : https://en.wikipedia.org/wiki/Ceph_%28storage%29
Updated by Loïc Dachary almost 9 years ago · 6 revisions