Remove proposed/ acls

I am reliably informed these are not used anymore.  Note, this
change updates All-Projects ACLs, so on approval, we should make
the corresponding change in Gerrit.

Change-Id: I1073663b8f80de8639a75b4b155258c1abed9df9

doc/source/gerrit.rst

@@ -218,7 +218,7 @@ High level goals:
 #. Members of Release Managers (Release Manager and delegates), and
    $PROJECT-milestone (PTL and release minded people) exclusively can
    perform full code review (blocking or approving: +/- 2), and submit
-   changes to be merged on pre-release proposed/* branches.
+   changes to be merged on pre-release stable/* branches.
 #. Full code review (+/- 2) of API projects (documentation of the API,
    not implementation of the API) should be available to the -core
    group of the corresponding implementation project as well as to the
@@ -306,15 +306,6 @@ Next, edit `project.config` to look like::
   submit = group Continuous Integration Tools
   submit = group Project Bootstrappers
 
-  [access "refs/heads/proposed/*"]
-  exclusiveGroupPermissions = label-Code-Review label-Workflow
-  label-Code-Review = -2..+2 group Project Bootstrappers
-  label-Code-Review = -2..+2 group Release Managers
-  label-Code-Review = -1..+1 group Registered Users
-  label-Workflow = +0..+1 group Project Bootstrappers
-  label-Workflow = +0..+1 group Release Managers
-  owner = group Release Managers
-
   [access "refs/meta/config"]
   read = group Project Owners
 

doc/source/jeepyb.rst

@@ -88,10 +88,6 @@ a single project you will want to do the following:
      label-Code-Review = -2..+2 group project-name-core
      label-Workflow = -1..+1 group project-name-core
 
-     [access "refs/heads/proposed/*"]
-     label-Code-Review = -2..+2 group project-name-release
-     label-Workflow = -1..+1 group project-name-release
-
      [receive]
      requireChangeId = true
      requireContributorAgreement = true