84eb58d367
We have the --type argument, where we can list which type of deliverables we want to be listed, but we don't have the opposite approach where we list the types that we DON'T want to be listed. This patch introduces the --except-type argument with wich we can list the deliverables with excluding some types, for example: $ list-deliverables --series epoxy --except-type tempest-plugin The above command lists all deliverables from 2025.1 Epoxy series that aren't tempest-plugins. Change-Id: If00115d3e7de055da2bd7a2dcd08298f70bd5989 |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
playbooks | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.