Document client lib tag permissions.
Document the process for granting tag permissions to the drivers group for client libraries, which are used to trigger releases. Change-Id: Ie64990461dd0992fea2481108b70f343f0623bb7
This commit is contained in:
parent
a0d9e1e29d
commit
a351a31ffb
@ -795,6 +795,9 @@ High level goals:
|
||||
#. Full code review of stable branches should be available to the
|
||||
-core group of the project as well as the openstack-stable-maint
|
||||
group.
|
||||
#. Drivers (PTL and delegates) of client library projects should be
|
||||
able to add tags (which are automatically used to trigger
|
||||
releases).
|
||||
|
||||
To manage API project permissions collectively across projects, API
|
||||
projects are reparented to the "API-Projects" meta-project instead of
|
||||
@ -855,6 +858,8 @@ These permissions try to achieve the high level goals::
|
||||
project foo:
|
||||
refs/*
|
||||
owner: Administrators
|
||||
create reference: foo-drivers [client library only]
|
||||
push annotated tag: foo-drivers [client library only]
|
||||
|
||||
refs/heads/*
|
||||
label code review -2/+2: foo-core
|
||||
@ -985,6 +990,14 @@ And make entries in `groups` for each one of them. Next, edit
|
||||
label-Code-Review = -2..+2 group $PROJECT-drivers
|
||||
label-Approved = +0..+1 group $PROJECT-drivers
|
||||
|
||||
If the project is for a client library, the `refs/*` section of
|
||||
`project.config` should look like::
|
||||
|
||||
[access "refs/*"]
|
||||
owner = group Administrators
|
||||
create = group $PROJECT-drivers
|
||||
pushTag = group $PROJECT-drivers
|
||||
|
||||
Replace $PROJECT with the name of the project.
|
||||
|
||||
Finally, commit the changes and push the config back up to Gerrit::
|
||||
|
Loading…
Reference in New Issue
Block a user