b54fc8defe
Introduce a new tool to list inconsistencies between projects.yaml in governance repository and deliverables in the releases repository. Sometimes projects.yaml defines release-managed deliverables, but the release team is not handling them. Sometimes, the release management team handles deliverables which are not officially produced by an OpenStack project team, and should probably not be listed on releases.o.o. This tool lists both types of inconsistencies, and can be integrated to release management process so that they are handled before becoming an issue. NB: Once ready, this tool could be used to replace the "membership freeze check" tool which only looked at some of those inconsistencies. Change-Id: Id263f0c91f872111fe997e2b8a1088b61033d114 |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
README.rst
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.