HOWTO » History » Version 71
Loïc Dachary, 09/02/2015 10:49 AM
1 | 15 | Loïc Dachary | h3. Introduction |
---|---|---|---|
2 | 1 | Loïc Dachary | |
3 | 51 | Loïc Dachary | Backporting and the maintenance of a stable release begins when a new "stable Ceph release":http://ceph.com/docs/master/releases is published. Commits from the master branch are cherry-picked to the stable branch and run through integration and upgrade tests. After a few weeks a "point release":http://ceph.com/docs/master/releases is published. This repeats until the "the stable release is retired":http://ceph.com/docs/master/releases. Backporting is focused on fixing bugs and development on the master branch is expected to add new features but both share the "same workflow":http://ceph.com/docs/master/dev/development-workflow/. |
4 | 16 | Loïc Dachary | |
5 | 24 | Loïc Dachary | h3. Overview of the backports in progress |
6 | |||
7 | 71 | Loïc Dachary | * *infernalis* -complete- -backport status- "backports":http://tracker.ceph.com/projects/ceph/issues?query_id=82 and "pending issues":http://tracker.ceph.com/projects/ceph/issues?query_id=83 and "pull requests":https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Ainfernalis |
8 | * *hammer* "complete":http://tracker.ceph.com/versions/495 "backport status":http://tracker.ceph.com/issues/12701 and "backports":http://tracker.ceph.com/projects/ceph/issues?query_id=78 and "pending issues":http://tracker.ceph.com/projects/ceph/issues?query_id=77 and "pull requests":https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Ahammer |
||
9 | * *firefly* "complete":http://tracker.ceph.com/versions/480 "backport status":http://tracker.ceph.com/issues/11644 and "backports":http://tracker.ceph.com/projects/ceph/issues?query_id=79 "pending issues":http://tracker.ceph.com/projects/ceph/issues?query_id=75 and "pull requests":https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Afirefly |
||
10 | 24 | Loïc Dachary | |
11 | 32 | Loïc Dachary | h3. Leads |
12 | |||
13 | 35 | Loïc Dachary | * Ceph : Sage Weil |
14 | 32 | Loïc Dachary | * rados : Samuel Just |
15 | * radosgw / rgw : Yehuda Sadeh |
||
16 | * CephFS / fs : Gregory Farnum |
||
17 | * RBD : Josh Durgin |
||
18 | 60 | Loïc Dachary | * build/ops : Ken Dreyer |
19 | 47 | Loïc Dachary | |
20 | 48 | Loïc Dachary | Note: It may be useful to know the leads of other projects which have a different lifecycle but depend on Ceph. For instance Gregory Meno is the lead of "Calamari":http://tracker.ceph.com/projects/calamari |
21 | 32 | Loïc Dachary | |
22 | 62 | Loïc Dachary | h3. Who's who |
23 | |||
24 | 65 | Loïc Dachary | Members of the "stable releases team":http://tracker.ceph.com/projects/ceph-releases are assigned the following roles as of August, 2015. |
25 | 62 | Loïc Dachary | |
26 | 67 | Loïc Dachary | * Abhishek Lekshmanan : helps other team members, when asked to |
27 | 64 | Loïc Dachary | * Abhishek Varshney : helps with the next hammer release |
28 | 62 | Loïc Dachary | * David Casier : runs the hammer upgrade suite |
29 | * Nathan Cutler : organizes the next firefly release |
||
30 | 67 | Loïc Dachary | * Loic Dachary : organizes the next hammer release |
31 | 62 | Loïc Dachary | * Sage Weil, Samuel Just, Yehuda Sadeh, Gregory Farnum, Josh Durgin, Ken Dreyer : leads |
32 | |||
33 | |||
34 | 26 | Loïc Dachary | h3. HOWTO |
35 | 23 | Loïc Dachary | |
36 | 1 | Loïc Dachary | The following describes in detail and in chronological order, the steps to follow for backporting and maintaining stable releases. |
37 | |||
38 | 23 | Loïc Dachary | h4. Add a new stable release |
39 | 19 | Loïc Dachary | |
40 | 1 | Loïc Dachary | * [[HOWTO start backporting a stable release]] |
41 | 15 | Loïc Dachary | |
42 | 23 | Loïc Dachary | h4. Add a new point release |
43 | 1 | Loïc Dachary | |
44 | 19 | Loïc Dachary | * [[HOWTO start working on a new point release]] |
45 | 15 | Loïc Dachary | |
46 | 23 | Loïc Dachary | h4. Prepare a new point release |
47 | 9 | Loïc Dachary | |
48 | 43 | Loïc Dachary | # [[HOWTO monitor the automated tests AKA nightlies]] |
49 | 22 | Loïc Dachary | # [[HOWTO schedule an issue for backporting]] |
50 | 30 | Loïc Dachary | # [[HOWTO document user visible changes]] |
51 | 1 | Loïc Dachary | # [[HOWTO backport commits]] |
52 | 19 | Loïc Dachary | # [[HOWTO populate the integration branch]] |
53 | 1 | Loïc Dachary | # [[HOWTO run integration and upgrade tests]] |
54 | 46 | Loïc Dachary | # [[HOWTO forensic analysis of integration and upgrade tests]] |
55 | 19 | Loïc Dachary | # [[HOWTO describe a test result]] inline or [[HOWTO summarize test results]] in a separate issue |
56 | 25 | Loïc Dachary | # [[HOWTO merge commits from the integration branch]] |
57 | 1 | Loïc Dachary | # [[HOWTO synchronize pull requests from different repositories]] |
58 | 27 | Loïc Dachary | # [[HOWTO resolve issues that are Pending Backport]] |
59 | 34 | Loïc Dachary | # [[HOWTO get the Ceph lead to decide if it is time for a point release]] |
60 | 31 | Loïc Dachary | # [[HOWTO get the leads to sign-off on a release]] |
61 | 33 | Loïc Dachary | # [[HOWTO write the release notes]] |
62 | 15 | Loïc Dachary | |
63 | 38 | Loïc Dachary | h4. Publish a stable release |
64 | |||
65 | 39 | Loïc Dachary | * Study https://github.com/ceph/ceph-build/ and http://jenkins.ceph.com/ to figure out how it is used to update http://ceph.com/debian-hammer/ and http://ceph.com/rpm-hammer/ |
66 | 40 | Loïc Dachary | * The jenkins job is http://jenkins.ceph.com/job/ceph/ and requires some setup |
67 | * The "ceph-jenkins-build":https://github.com/alfredodeza/ceph-jenkins-build/tree/master/ceph ansible setup does a bunch of things like "changing version numbers, creating a tag and pushing to the Jenkins GIT repository":https://github.com/alfredodeza/ceph-jenkins-build/blob/master/ceph/tasks/setup.yml |
||
68 | * once that tag is created that can be used to trigger a build in the jenkins ui when the build is completed you are required to run a bunch of scripts in the jenkins server they sign and re-index the repositories and then synchronize them with ceph/(rpm|debian)-$release. Those scripts need to be edited by hand depending on the type of release and where you are pushing them to (e.g. testing vs firefly vs hammer) |
||
69 | * for hammer a new repository was created by hand and it is "documented as a script":https://gist.github.com/alfredodeza/b8f8b94ea795f1a7169b |
||
70 | 38 | Loïc Dachary | |
71 | 23 | Loïc Dachary | h4. Retire a stable release |
72 | 15 | Loïc Dachary | |
73 | 21 | Loïc Dachary | * [[HOWTO retire a stable release]] |
74 | 41 | Loïc Dachary | |
75 | 54 | Nathan Cutler | h4. Recurring duties expected from backporters |
76 | 52 | Cron Tab | |
77 | 54 | Nathan Cutler | * [[HOWTO triage incoming backport pull requests]] |
78 | 58 | Nathan Cutler | * [[HOWTO triage incoming Pending backport issues]] |
79 | 70 | Loïc Dachary | * "fill in the missing releases":http://tracker.ceph.com/projects/ceph/issues?query_id=84 |
80 | 52 | Cron Tab | |
81 | 56 | Cron Tab | Backporters currently performing these duties (remove yourself when on vacation etc.): |
82 | |||
83 | * Loic Dachary : weekly |
||
84 | 57 | Nathan Cutler | * Nathan Cutler : weekly |
85 | 59 | Abhishek Lekshmanan | * Abhishek L : weekly |
86 | 56 | Cron Tab | |
87 | 41 | Loïc Dachary | h4. Organize the stable releases and backports team |
88 | |||
89 | * [[HOWTO become a new team member]] |
||
90 | * [[HOWTO retire from the team]] |