Project

General

Profile

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

Loïc Dachary, 03/06/2021 12:37 PM
format

1 1 Loïc Dachary
h3. Create a new version
2 1 Loïc Dachary
3 5 Loïc Dachary
* http://tracker.ceph.com/projects/ceph/versions/new
4 5 Loïc Dachary
* only set the name with **release version** (for instance **v0.80.10**)
5 10 Loïc Dachary
* select *Shared with subprojects*
6 1 Loïc Dachary
7 9 Loïc Dachary
h3. Decide who will drive the point release
8 9 Loïc Dachary
9 9 Loïc Dachary
There is no formal process. Someone volunteers and discuss it with [[HOWTO#Whos-who|other members of the team]], via e-mail or irc.
10 9 Loïc Dachary
11 1 Loïc Dachary
h3. Create new task
12 1 Loïc Dachary
13 1 Loïc Dachary
* http://tracker.ceph.com/projects/ceph-releases/issues/new
14 4 Loïc Dachary
* Title *release version* (for instance **firefly v0.80.10**)
15 1 Loïc Dachary
* Assign it to the "backporter":http://tracker.ceph.com/projects/ceph-releases responsible for it
16 14 Loïc Dachary
* Set the *Affected Versions* field to the version (for instance **v0.80.10**)
17 14 Loïc Dachary
* Set the priority to *Urgent* for releases that contain only a few backports that need to be published immediately and *High* otherwise
18 15 Loïc Dachary
19 1 Loïc Dachary
h3. Add a workflow section to the description
20 1 Loïc Dachary
21 16 Loïc Dachary
The issue is used to figure out at what point of the release workflow it currently is. The "development workflow":https://docs.ceph.com/en/latest/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 "nautilus v14.2.17":https://tracker.ceph.com/issues/49629
22 1 Loïc Dachary
23 17 Loïc Dachary
h4. Workflow
24 16 Loïc Dachary
25 16 Loïc Dachary
* "Preparing the release":https://docs.ceph.com/en/latest/dev/development-workflow/#preparing-a-new-release *TBD*
26 16 Loïc Dachary
* "Cutting the release":https://docs.ceph.com/en/latest/dev/development-workflow/#cutting-a-new-stable-release 
27 16 Loïc Dachary
** Abhishek/Yuri gets approval from all leads 
28 16 Loïc Dachary
*** Casey, rgw - *TBD*
29 16 Loïc Dachary
*** Patrick, fs - *TBD*
30 16 Loïc Dachary
*** Jason, rbd - *TBD*
31 16 Loïc Dachary
*** Neha, rados - *TBD*
32 16 Loïc Dachary
** Abhishek informs Yuri that the branch is ready for testing - sha1:
33 16 Loïc Dachary
Current SHA1: see in note below
34 16 Loïc Dachary
** Yuri runs additional integration tests - *TBD*
35 16 Loïc Dachary
*** If Yuri discovers new bugs that need to be backported urgently (i.e. their priority is set to *Urgent* or *Immediate*), the release goes back to being prepared; it was not ready after all
36 16 Loïc Dachary
** Yuri informs Sage, David that the branch is ready for release - *TBD*
37 16 Loïc Dachary
** Someone creates the packages and sets the release tag - *TBD*
38 16 Loïc Dachary
** Someone writes and commits the release notes - *TBD*
39 16 Loïc Dachary
** Someone sends out release announcement email - *TBD*
40 16 Loïc Dachary
** Someone posts release announcement on https://ceph.com/community/blog - *TBD*
41 16 Loïc Dachary
42 17 Loïc Dachary
h4. Release information
43 16 Loïc Dachary
44 16 Loïc Dachary
** branch to build from: nautilus, commit: 
45 16 Loïc Dachary
** version: v14.2.17
46 16 Loïc Dachary
** type of release: point release
47 16 Loïc Dachary
** where to publish the release: http://download.ceph.com/
48 1 Loïc Dachary
49 2 Loïc Dachary
h3. Add a release information template to the description
50 1 Loïc Dachary
51 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
52 2 Loïc Dachary
53 1 Loïc Dachary
* branch to build from: firefly, commit:???
54 1 Loïc Dachary
* version: v0.80.10
55 1 Loïc Dachary
* type of release: point release
56 13 Loïc Dachary
* where to publish the release: http://download.ceph.com/debian-$release and http://download.ceph.com/rpm-$release