HOWTO start backporting a stable release » History » Version 4
Loïc Dachary, 04/13/2015 12:55 PM
1 | 1 | Loïc Dachary | h3. Introduction |
---|---|---|---|
2 | |||
3 | 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. |
||
4 | |||
5 | h3. Add a new release in redmine |
||
6 | |||
7 | 2 | Loïc Dachary | * http://tracker.ceph.com/rb/release/ceph-releases/new |
8 | * the name of the release is the name of the ceph release, all lowercase |
||
9 | * the start date is the month when the stable release was first published |
||
10 | * 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 |
||
11 | 3 | Loïc Dachary | * Update the [[HOWTO|HOWTO landing page]] |
12 | * Update the "project overview":http://tracker.ceph.com/projects/ceph-releases/settings/info |
||
13 | 1 | Loïc Dachary | |
14 | h3. Add a new integration branch in git |
||
15 | |||
16 | For instance "firefly-backports":https://ceph.com/git/?p=ceph.git;a=shortlog;h=refs/heads/firefly-backports |
||
17 | |||
18 | * release=firefly |
||
19 | * git checkout -b $release-backports $release |
||
20 | * git push ceph $release-backports |
||
21 | 3 | Loïc Dachary | |
22 | h3. Create a new version |
||
23 | |||
24 | * Add something like *hammer v0.94.1* in http://tracker.ceph.com/projects/ceph-releases/settings/versions |
||
25 | * Create a new issue to track the progress, copying an existing one (for instance http://tracker.ceph.com/issues/11353) |
||
26 | * Update the [[HOWTO|HOWTO landing page]] |
||
27 | 4 | Loïc Dachary | |
28 | h3. Update websites with the new release |
||
29 | |||
30 | * ceph.com : http://ceph.com/resources/downloads/ |
||
31 | * wikipediat : https://en.wikipedia.org/wiki/Ceph_%28storage%29 |