HOWTO become a new team member » History » Revision 2
Revision 1 (Loïc Dachary, 04/17/2015 08:26 AM) → Revision 2/8 (Loïc Dachary, 04/17/2015 08:31 AM)
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.
* Add the team member to the "ceph backporter group":http://tracker.ceph.com/groups/2458/edit
* Explain the structure of the "stable releases and backports":http://tracker.ceph.com/projects/ceph-releases/ project
** "Backporter manual":http://tracker.ceph.com/projects/ceph-releases/wiki
** "Ceph releases":http://ceph.com/docs/master/releases/
** "Ceph development workflow":http://ceph.com/docs/master/dev/development-workflow/
* 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)
* 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