openstack/releases
Code Issues Proposed changes

Add precisions to the aclmanager update

Browse Source 
Update instructions about the aclmanager dance between M-2
and M-3, so that we don't repeat the Pike mistakes.

Change-Id: I5a66ac3a67e2a1f5f8eb83f45d5e710545b5ca6c
This commit is contained in:
Thierry Carrez 2017-07-12 18:24:58 +02:00
parent ac8df19396
commit a493f75647
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
PROCESS.rst
View File

@ -93,16 +93,25 @@ Between Milestone-2 and Milestone-3
generated (for all release:cycle-with-milestones deliverables)
with::
tox -e aclmanager -- acls /path/to/openstack-infra/project-config
tox -e aclmanager -- acls /path/to/project-config
2. Set the population of all $project-release-branch groups to the
Double-check that all references to the previous stable/$old
are all removed from project-config gerrit ACLs, as some may
have changed release models and kept stale entries::
grep stable/$old /path/to/project-config/gerrit/acls/openstack/*
2. Once the above patch merges (and only then!), set the population
of all $project-release-branch groups to the
"Release Managers" group and $project-release. This can be done
(for all release:cycle-with-milestones deliverables) by running
``aclmanager.py``::
tox -e aclmanager -- groups pre_release $user
($user being your Gerrit username)
($user being your Gerrit username). It will prompt you for your
Gerrit HTTP password, which you can see/generate at
https://review.openstack.org/#/settings/http-password.
3. Ask the release liaisons for the affected teams to update the
contents of their $project-release groups. For new projects in