HOWTO become a new team member » History » Version 3
Loïc Dachary, 05/15/2015 11:37 AM
1 | 1 | Loïc Dachary | A "team member":http://tracker.ceph.com/projects/ceph-releases is an individual willing to dedicate at least one day a week to backport issues and publish stable releases. The team member responsibility is to follow the process described in the "HOWTO":http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO and make it as easy as possible for the other parties involved to publish the next stable release. A team member is not expected to be an expert in backporting complex commits but is committed to reduce the backport overhead imposed on developers. If a team member is temporarily unable to fulfil his duties, Loic Dachary can be requested to act as a replacement in the meantime. |
---|---|---|---|
2 | |||
3 | * Add the team member to the "ceph backporter group":http://tracker.ceph.com/groups/2458/edit |
||
4 | * Explain the structure of the "stable releases and backports":http://tracker.ceph.com/projects/ceph-releases/ project |
||
5 | ** "Backporter manual":http://tracker.ceph.com/projects/ceph-releases/wiki |
||
6 | ** "Ceph releases":http://ceph.com/docs/master/releases/ |
||
7 | ** "Ceph development workflow":http://ceph.com/docs/master/dev/development-workflow/ |
||
8 | 2 | Loïc Dachary | * The new team member is assigned the issue tracking the progress of a stable release (for instance "firefly v0.80.10":http://tracker.ceph.com/issues/11090) |
9 | * During this first stable release the new team member is mentored through "each step":http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO and is expected to gradually take control of the process |
||
10 | 3 | Loïc Dachary | |
11 | A few tasks require additional permissions and Loic Dachary can be used as a proxy: |
||
12 | |||
13 | * Being a member of the Ceph team at http://github.com/ceph/ceph to |
||
14 | ** assign issues, set labels and milestones |
||
15 | ** push the $release-backport branch content (so that packages required by teuthology are built by http://ceph.com/gitbuilder.cgi) |
||
16 | * Being a member of the Ceph team at http://tracker.ceph.com/ to |
||
17 | ** update issues in the Ceph project to update the backport field, assign issues and close pending backport issues |
||
18 | * Being an admin of http://tracker.ceph.com/ to |
||
19 | ** create or update publicly available custom search |
||
20 | * Have VPN access to the community lab (sepia, typica) to |
||
21 | ** schedule teuthology suites |
||
22 | ** query paddles |