From 77ef1aeb9f93c472147c4d9189a4718d9c4ec3be Mon Sep 17 00:00:00 2001 From: Russell Bryant Date: Mon, 9 Nov 2015 09:31:36 -0500 Subject: [PATCH] Document the neutron-release team. Gerrit includes a neutron-release team. Document what this team means today. Also propose that this team have merge rights to *all* Neutron git repos so that a small group has the ability to quickly unblock things if needed, which is especially important around release time. Change-Id: Id3d4d051278930841f64a4153e40a2dd3d893e44 Signed-off-by: Russell Bryant --- doc/source/policies/neutron-teams.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/source/policies/neutron-teams.rst b/doc/source/policies/neutron-teams.rst index 6f55e862265..0be57193a80 100644 --- a/doc/source/policies/neutron-teams.rst +++ b/doc/source/policies/neutron-teams.rst @@ -262,6 +262,20 @@ that govern contributions to the Neutron project as a whole. The team to go over RFE's and discuss the project roadmap. Anyone is welcome to join and/or read the meeting notes. +Release Team +------------ + +The `release team `_ is +a group of people with some additional gerrit permissions primarily aimed at +allowing release management of Neutron sub-projects. These permissions include: + +* Ability to push signed tags to sub-projects whose releases are managed by the + Neutron release team as opposed to the OpenStack release team. +* Ability to push merge commits for Neutron or other sub-projects. +* Ability to approve changes in all Neutron git repositories. This is required + as the team needs to be able to quickly unblock things if needed, especially + at release time. + Code Merge Responsibilities ===========================