Ceph » Stable releases

Welcome package¶

A team member 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 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
• Explain the structure of the stable releases and backports project
  • Backporter manual
  • Ceph releases
  • Ceph development workflow
• The new team member is assigned the issue tracking the progress of a stable release (for instance firefly v0.80.10)
• During this first stable release the new team member is mentored through each step and is expected to gradually take control of the process

Permissions¶

A few tasks require additional permissions and Loic Dachary can be used as a proxy when necessary:

• Being a member of the Ceph team at http://github.com/ceph/ceph to
  • assign issues, set labels and milestones
  • push the $release-backport branch content (so that packages required by teuthology are built by http://ceph.com/gitbuilder.cgi)
• Being a member of the Ceph team at http://tracker.ceph.com/ to
  • update issues in the Ceph project to update the backport field, assign issues and close pending backport issues
• Being an admin of http://tracker.ceph.com/ to
  • create or update publicly available custom search
• Have VPN access to the community lab (sepia, typica) to
  • schedule teuthology suites
  • query paddles