From 96b0a4c2cd1c8e0e93fd928eaeee8b496a80068a Mon Sep 17 00:00:00 2001
From: Jeremy Stanley <fungi@yuggoth.org>
Date: Fri, 12 Dec 2014 20:12:36 +0000
Subject: [PATCH] Documentation reflects new stable-maint workflow
Equivalent cleanup has already been performed in the All-Projects
ACL, in the wake of Id127d24e4428be8b450de277dc55df20349aab13
merging.
Change-Id: Ie89810c728e9cc39e6b3e05d312c9c1818e7d984
---
doc/source/gerrit.rst | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/doc/source/gerrit.rst b/doc/source/gerrit.rst
index a7265d7d13..d3363a078e 100644
--- a/doc/source/gerrit.rst
+++ b/doc/source/gerrit.rst
@@ -93,9 +93,6 @@ other CI tools that get +2/-2 access on reviews.
The `Release Managers` group is used for release managers.
-The `Stable Maintainers` group is used for people maintaining stable
-branches - often distinct from the folk maintaining projects.
-
Users
-----
@@ -207,8 +204,7 @@ High level goals:
group of the corresponding implementation project as well as to the
OpenStack Documentation Coordinators.
#. Full code review of stable branches should be available to the
- -core group of the project as well as the Stable Maintainers
- group.
+ -stable-maint group of the project.
#. Drivers (PTL and delegates) of client library projects should be
able to add tags (which are automatically used to trigger
releases).
@@ -297,16 +293,6 @@ Next, edit `project.config` to look like::
label-Workflow = +0..+1 group Release Managers
owner = group Release Managers
- [access "refs/heads/stable/*"]
- exclusiveGroupPermissions = label-Code-Review label-Workflow
- forgeAuthor = group openstack-stable-maint
- forgeCommitter = group openstack-stable-maint
- label-Code-Review = -2..+2 group Project Bootstrappers
- label-Code-Review = -2..+2 group openstack-stable-maint
- label-Code-Review = -1..+1 group Registered Users
- label-Workflow = +0..+1 group Project Bootstrappers
- label-Workflow = +0..+1 group openstack-stable-maint
-
[access "refs/meta/config"]
read = group Project Owners