b7aaef88c8
Change e2fbcad77636996a1205adab032407e10e642bc4 added a new config option ``barbican`` which enables/disables barbican for cinder tempest plugin. This option is a duplicate of an already existing option in barbican tempest plugin and caused an issue when both cinder and barbican tempest plugin are run together. This issue is fixed by change 89823d9868a58da23bbc0c8d9020b0adaafda32b which is merged and a new release is tagged based on it. Change-Id: I2b1d9d3f6d4b989f3555edacb196353de89ef41b |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
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.