openstack/releases
Code Issues Proposed changes

Use governance_consistency.py for MembershipFreeze

Browse Source 
The new governance_consistency.py tool lists all inconsistencies
between deliverables defined in openstack/releases and deliverables
defined in openstack/governance. Using it instead of the
membership_freeze_test tool (which only listed deliverables defined
in governance that did not have a corresponding deliverable file)
gives us the chance to fix all inconsistencies before milestone-2.

Change-Id: I34c2454082054b6e49edf16784e0e9213799ecc1
This commit is contained in:
Thierry Carrez
2020-02-25 15:50:33 +01:00
committed by Jean-Philippe Evrard
parent 2c5254e33f
commit 3c0c72be8f
1 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -257,18 +257,28 @@ Between Milestone-1 and Milestone-2
Week before Milestone-2 Week before Milestone-2
======================= =======================
#. Ahead of MembershipFreeze, run ``membership_freeze_test`` to check for #. Ahead of MembershipFreeze, run ``governance_consistency.py``::
any new deliverable in governance that has not been released yet::
tox -e membership_freeze_test -- $series ~/branches/governance/reference/projects.yaml python3 tools/governance_consistency.py $series $project_yaml_file
Those should either be tagged as a release management exception if they do This tool will list all inconsistencies between the deliverables described
in the governance's reference "projects.yaml" file and the deliverables
defined in the $series directory or the _independent directory.
There should ideally be none.
For deliverables defined in governance but not in deliverable files,
they should either be tagged as a release management exception if they do
not need to be released (see ``release-management`` key in the governance not need to be released (see ``release-management`` key in the governance
projects.yaml file) or an empty deliverable file should be added to the 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 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 to be released in the next release and will be reconsidered at the next
cycle. cycle.
For deliverables defined in deliverable files but not in (active)
governance, their deliverable file should generally be removed from the
$series directory, or marked release-model:abandoned if present in the
_independent directory.
#. Send the following weekly email content:: #. Send the following weekly email content::
Development Focus Development Focus