HOWTO start backporting a stable release » History » Version 2
Loïc Dachary, 03/26/2015 10:11 AM
| 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 | 1 | Loïc Dachary | |
| 12 | h3. Add a new integration branch in git |
||
| 13 | |||
| 14 | For instance "firefly-backports":https://ceph.com/git/?p=ceph.git;a=shortlog;h=refs/heads/firefly-backports |
||
| 15 | |||
| 16 | * release=firefly |
||
| 17 | * git checkout -b $release-backports $release |
||
| 18 | * git push ceph $release-backports |