opendev/infra-manual
Code Issues Proposed changes

update project creator's guide section on tag ACLs

Browse Source 
The release management team wants all official projects to use the
openstack/releases repository for requesting releases. Update the
project creator's guide to reflect this in the instructions for setting
ACLs for new repositories.

Change-Id: I6820cdd3bc8524005bb6c5fa67c400fe7c0028a3
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-04-13 18:03:52 -04:00
parent 8e2eda277a
commit 13afe2cdf3
1 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/source/creators.rst
View File

@ -302,12 +302,20 @@ Add the project to the master projects list
Add Gerrit permissions
----------------------
Each project should have two gerrit groups. The first,
"<projectname>-core", is the normal core group, with permission to
+2 changes. The second, "<projectname>-release" is a small group of
the primary maintainers with permission to push tags to trigger
releases. Libraries for projects managed by the release team do not need
this group, and should use ``library-release`` instead.
Each project should have a gerrit group "<projectname>-core",
containing the normal core group, with permission to
+2 changes.
Libraries for official projects should be configured so the
``library-release`` team has tagging rights.
Other official projects should be configured so that tagging rights
use the default settings, allowing the "``Release Managers``" team to
push tags.
For unofficial projects, a second "<projectname>-release" team should
be created and populated with a small group of the primary maintainers
with permission to push tags to trigger releases.
Create a ``gerrit/acls/openstack/<projectname>.config`` as
explained in the following sections.
@ -355,9 +363,9 @@ containing::
[access "refs/tags/*"]
pushSignedTag = group library-release
For non-library projects, or projects not managed by the release team,
you can allow the project-specific release team to create tags by
adding a new section containing::
For non-library projects, or unofficial projects, you can allow the
project-specific release team to create tags by adding a new section
containing::
[access "refs/tags/*"]
pushSignedTag = group <projectname>-release