openstack/releases
Code Issues Proposed changes

Merge "Add script to facilitate MembershipFreeze handling"

Browse Source
This commit is contained in:
Zuul
2019-01-16 22:50:13 +00:00
committed by Gerrit Code Review
parent e9c844975f 50258742c9
commit 3f0d1cc05f
4 changed files with 109 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/reference/process.rst
View File

@@ -74,6 +74,17 @@ Between Milestone-1 and Milestone-2
List teams that still haven't done a library release yet and remind
them of the milestone-2 deadline.
5. Ahead of MembershipFreeze, run membership_freeze_test to check for
any new deliverable in governance that has not been released yet::
tox -e membership_freeze_test -- $series ~/branches/governance/reference/projects.yaml
Those should either get a release management exception (see
release-management key in the governance projects.yaml file) or an
empty deliverable file should be added to the series so that we can
properly track it. Leftovers are considered too young to be released
in the next release and will be reconsidered at the next cycle.
Milestone-2
===========

19
doc/source/reference/using.rst
View File

@@ -603,6 +603,25 @@ To set the pre-release group membership:
tox -e aclmanager -- groups pre_release ttx
tools/membership_freeze_test.py
--------------------------------
A script to test for new deliverables in governance that were
never under release management and therefore escape any form of
release management tracking.
Those need to be checked around milestone-2 (before MembershipFreeze)
so that we create deliverable files for them if they are to be part of
the final release.
Example:
To check for Stein release:
::
tox -e membership_freeze_test -- stein ~/branches/governance/reference/projects.yaml
propose-final-releases
----------------------