Project

General

Profile

HOWTO start working on a new point release » History » Version 2

Loïc Dachary, 03/26/2015 10:27 AM

1 1 Loïc Dachary
h3. Create a new version
2 1 Loïc Dachary
3 2 Loïc Dachary
* http://tracker.ceph.com/projects/ceph-releases/versions/new
4 2 Loïc Dachary
* only set the name with **release version** (for instance **firefly v0.80.10**)
5 1 Loïc Dachary
6 1 Loïc Dachary
h3. Create new task
7 1 Loïc Dachary
8 1 Loïc Dachary
* http://tracker.ceph.com/projects/ceph-releases/issues/new
9 1 Loïc Dachary
* Title **release version** (for instance **firefly v0.80.10**)
10 1 Loïc Dachary
* Assign it to the "backporter":http://tracker.ceph.com/projects/ceph-releases responsible for it
11 1 Loïc Dachary
* Set the **Release** field to the release (for instance **firefly**)
12 1 Loïc Dachary
* Set the **Target version** field to the version (for instance **firefly v0.80.10**)
13 1 Loïc Dachary
14 1 Loïc Dachary
h3. Add a workflow section to the description
15 1 Loïc Dachary
16 1 Loïc Dachary
The issue is used to figure out at what point of the release workflow it currently is. The "development workflow":http://ceph.com/docs/master/dev/development-workflow/ must be copied and edited to reflect the specifics of the version being released (i.e. replacing roles by names of people responsible for a given component at this point in time for instance). Here is an example from "firefly v0.80.10":http://tracker.ceph.com/issues/11090
17 1 Loïc Dachary
18 1 Loïc Dachary
* "Preparing the release":http://ceph.com/docs/master/dev/development-workflow/#preparing-a-new-release
19 1 Loïc Dachary
* "Cutting the release":http://ceph.com/docs/master/dev/development-workflow/#cutting-a-new-stable-release
20 1 Loïc Dachary
** Loic gets approval from all leads
21 1 Loïc Dachary
*** Yehuda, rgw: 
22 1 Loïc Dachary
*** Gregory, CephFS:
23 1 Loïc Dachary
*** Josh, RBD:
24 1 Loïc Dachary
*** Sam, rados:
25 1 Loïc Dachary
** Sage writes and commits the release notes 
26 1 Loïc Dachary
** Loic informs Yuri that the branch is ready for testing 
27 1 Loïc Dachary
** Yuri runs additional integration tests
28 1 Loïc Dachary
** If Yuri discovers new bugs with severity Critical, the relase goes back to being prepared, it was not ready after all
29 1 Loïc Dachary
** Yuri informs Alfredo that the branch is ready for release
30 1 Loïc Dachary
** Alfredo creates the packages and sets the release tag 
31 1 Loïc Dachary
32 2 Loïc Dachary
h3. Add a release information template to the description
33 1 Loïc Dachary
34 2 Loïc Dachary
This will be used by the person responsible for the publishing the release. Although it is largely redundant with information from the context, it can convenientely be copy pasted and does not require any understanding of the conventions used for backporting. The release manager can publish the release with just this information and nothing else. The commit hash (**???**) below is in the release branch and has "received approval by everyone involved":http://ceph.com/docs/master/dev/development-workflow/#cutting-a-new-stable-release
35 2 Loïc Dachary
36 1 Loïc Dachary
* branch to build from: firefly, commit:???
37 1 Loïc Dachary
* version: v0.80.10
38 1 Loïc Dachary
* type of release: point release
39 2 Loïc Dachary
* where to publish the release: debian/rpm-$release and debian/debian-$release