This change updates the defintion of Review-priority
to match the new defintion in our contrib docs.
Change-Id: I2b172439e959753b6a62483703bfa8bd93175187
This change adds a Review Priority label to all nova deliverables
currently under acl control in the project config repo.
The ability set the new label is granted only to the core
and stable core teams for the updated repos.
Change-Id: I2fd7a6387d2f50eeeb8cef513df19b5696cce55b
This patch series move openstack/* projects from All-Projects ACL to
meta-config ACL, which is created especially for the Release Managers
group.
Change-Id: Ib22337a6309bc420b3bc3412e04c9452c34d5ed0
Some repos have ACLs with groups that contain the stable-maint-core
group, while others do not include the group at all. All governed repos
should include this team, even if they don't assert
stable:follows-policy so stable branch issues can be resolved as needed.
To make it consistent and clear, this adds stable-maint-core directly to
the ACLs for all repos under governance.
Change-Id: Ifdc429e2c9609475584f0473828d41d3f1067c72
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This reverts commit fa5ac08128.
There is no longer need for a specific stable/queens ACL, as
post-release we can default to the general stable/* rule instead.
Change-Id: I34bc206eca5a04cc924e8e33b2791bd9214ce13b
As part of the usual release process, add specific ACL for
the stable/queens branch, so that we can transfer control from
release managers to stable branch managers around release time.
This change will be reverted post-release once the specific ACL
is no longer needed.
For more details, see:
http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst#n86
Change-Id: I222390e96759f5dc83a41cdc606d5e964f2b011d
This removes stable/pike-specific ACLs that were used to handle
ACL transition between releae and stable team around Pike
release.
Change-Id: I2a6f17d0224c16408c7326bfcb5a6e6b4f35c4b1
For cycle-with-milestones deliverables, define a specific
ACL for stable/pike pointing to the $project-release-branch
group. Pre-release, that group will include Release Managers
and $project-release (to give control to release teams).
Post-release that group will contain $project-stable-maint,
to give control to stable teams).
Change-Id: I9fa69e035d3ba50f8171b510bc9da753d48486bb
Following the end-of-cycle process describe in
openstack/releases/PROCESS.rst, set the gerrit ACLs for the stable
branches so the appropriate team members can approve patches during the
release candidate phase. The stable/ocata branches will be created in
a few weeks.
Change-Id: I80e1b68c881bfd27b6ad06aa6b5f2a216bd81a63
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This reverts commit dee868e4bb,
but also the stable/newton ACL introduced for networking-hyperv
in 01de6ee4f9.
Change-Id: Icb576a4b51fd68fac1e63e18feaa9cab77f04d4d
Set up a temporary ACL rule for handling the upcoming
stable/newton release branches, for milestone-driven projects
which will go through a release candidate phase.
The $project-release-branch groups will have 'Release Managers'
as its initial member and admin. We'll add PTLs and release
liaisons to the groups pre-release, then add the stable maintenance
team at release time. Then the temporary ACLs will be removed.
This process lets us handle the transition from release branch to
stable branch gracefully and without too much sync points between
infra and release teams.
Change-Id: I16ab679ee7b1f9018299659ecdc03b089600f701
Set up (temporary) pre-release ACLs for the soon-to-be-created
stable/mitaka branches (only for managed projects following the
milestones-driven release model).
This will be reverted post-release as we let stable maintenance
teams take over control over stabel branches.
Change-Id: Ia284ecddc497fbee86dc17f9f0b9f7c07293626f
Whenever a project-specific ACL declares exclusiveGroupPermissions
on some permission, it can block other valid uses of that permission
which would otherwise be inherited from the All-Projects pseudoACL.
Make sure that Project Bootstrappers retains access to abandon,
-2..+2 on label-Code-Review and -1..+1 on label-Workflow. Also make
sure Change Owners can still abandon and add -1..0 on
label-Workflow, and that Registered Users can always -1..+1 on
label-Code-Review.
This change corrects existing ACLs to meet the above criteria, and
also introduces a normalization rule to prevent regression.
Change-Id: I2eecb7028bcab7d5d82ad4155a775a9b2daa441f
All these changes are needed since they are in a group with exclusiveGroupPermissions.
This reverts commit 26ceb615a8.
Change-Id: Ie9cc164a45c5ae020d3b032ff7b4020e3c9a44b9
Since the upgrade to 2.11 this is redundant and casuses a problem in
some repos as this masks the (correct) internal group.
See discussion in: https://review.openstack.org/#/c/278521/
Change-Id: Ifc83b3ec1dead300c3983ca2b6bfdec6b1d99780
revert change I88fc2d2cdd708faa0a0d2fc8b00d77b53deb49d4 and give
karma back to those who need to maintain the stable branches
Note: Trove and Ceilometer needs to be done in subsequent reviews
as they are not released yet.
Change-Id: Ia55f5e6b6e67cf412ce6f653a70d068ec2acaf1b
Set up temporary pre-release stable/liberty ACLs since the
branch is currently a release branch until final release.
Change-Id: I88fc2d2cdd708faa0a0d2fc8b00d77b53deb49d4
Remove the stable/kilo temporarily release management ACL sections
but don't restore the old proposed/* sections since they're no
longer needed either. At least in spirit....
This reverts commit 639ec1d17e.
This reverts commit fb04574fc0.
This reverts commit 774f236cf4.
Change-Id: Ifb5e8ec6175ad0623db9e3c02883255c98149dab
...only Project Bootstrappers.
Correct the ACL normalization script oversight which led to this
unfortunate mistake, and clean up the resulting mess.
Change-Id: I391ead734d0cd28277581d54f254718c3e36d4b0
The proposed/kilo branches of integrated release projects will not
be used this cycle. Instead we're going straight into stable/kilo
but keeping the access controls we had over the old proposed
branches for now. This change can be reverted once Kilo is released,
to return control to teh stable branch maintainers thereafter.
Change-Id: Iaced68397d700d19a3f715de458bd83cbf78cf39
Now that all registered users have the rebase button, it's no longer
necessary to add explicitly in Gerrit ACLs.
Change-Id: Ib104a3f170b287bcf2215e2f5c0f31fe8234a4a5
Depends-On: Iefff52be4d12390be372429d6ebc48704c379630
This is the result of running:
find gerrit/acls/ -type f -name "*.config" -exec \
./tools/normalize_acl.py {} 1 2 3 4 5 6 \;
Some recent changes were not normalized ;(
Change-Id: I08f5c173c70903e9e2a006bf2327db97d9fc8b46
This is the result of running:
find gerrit/acls/ -type f -name "*.config" \
-exec ./tools/normalize_acl.py {} 1 2 3 4 5 6 \;
Change-Id: Ic281a233aae06b27096d315831e45bb3499a95fb
As discussed in Paris and subsequently discussed on the mailing-list,
switch stable branch maintenance to project-specific teams under the
guidance and leadership of the stable-maint-core team.
All $PROJECT-stable-maint teams in Gerrit should be owned by
stable-maint-core which will vet the addition of members to make sure
they are aware of the Stable Branch policy.
Remarks:
- Sahara was already using their own team, proposed change will align
them to use a specific team instead.
- Designate is still incubated and therefore stable-maint-core doesn't
own their stable branches yet. Proposed change fixes ACL to reflect
that.
- All projects still inherit openstack-stable-maint from the
all-projects ACL, but this will be removed once the transition is
over.
Reference:
http://lists.openstack.org/pipermail/openstack-dev/2014-November/050390.html
Change-Id: Id127d24e4428be8b450de277dc55df20349aab13
The projects that have their ACLs modified here have had third party CI
vote on them in the last 3 months. Add project specific CI group ACLs so
that these projects can directly manage which accounts are allowed to
vote on them.
Change-Id: Iaf9cbb86cd3077f28bf3c5f02de4718314ac1eef
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3
Sean Mooney