From 104ecfdf2cc86d1168a4edf98f26dac413c41671 Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann Date: Tue, 22 Mar 2022 15:38:13 -0500 Subject: [PATCH] Modify the project specific stable team management In Xena, TC passed the resolution about enabling the project team manage their stable core team. - https://governance.openstack.org/tc/resolutions/20210923-stable-core-team.html This commits relfects that resolution in stable branch policy document. Change-Id: I43d41cd9a1e0af0b0f2e4fc145f97c3ff4f76f8e --- doc/source/stable-branches.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/source/stable-branches.rst b/doc/source/stable-branches.rst index d8d29b7..a4c314c 100644 --- a/doc/source/stable-branches.rst +++ b/doc/source/stable-branches.rst @@ -193,10 +193,11 @@ Each project with a stable branch will have a project-specific stable maintenance Gerrit team called PROJECTNAME-stable-maint. This team will have CodeReview+2 and Workflow+1 rights over the stable branches, and be in charge of reviewing backports for a given project, following -the rules of the stable branch policy. Originally that group should be -the project Stable Branch Cross-Project Liaison + the stable maintenance core -team. Those groups are managed by the stable maintenance core team, names are -added after the suggestion of the Stable Branch cross-project liaison. +the rules of the stable branch policy. That group should be the project +Stable Branch core (not necessary to be master core) + the stable maintenance +core team. That group is managed by the project team like they manage their +master branch core team. To manage that group or stable policies, they can +consult with the stable maintenance core team. Stable Maintenance Core team ----------------------------