Release requests and history tracking
Go to file
Sean McGinnis 493b7bf33a
Update to latest hacking for pep8 checks
This updates the version of hacking we are using for our linting and
addresses various issues that the latest version flags.

Change-Id: I95ed73411e96451bc447e1b5858b0466fb8f10a9
Signed-off-by: Sean McGinnis <>
2020-07-27 16:33:03 -05:00
data Merge "Remove congress deliverables from Victoria release" 2020-06-18 00:10:28 +00:00
deliverables Merge "Release tripleo-operator-ansible" 2020-07-27 20:07:19 +00:00
doc Update Summit to be virtual event 2020-07-24 09:46:28 +00:00
openstack_releases Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Switch to victoria job template 2020-06-02 14:28:30 -05:00
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Update README.rst for better looks 2019-11-13 16:51:02 +01:00
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05:00
requirements.txt Cap jsonschema 3.2.0 as the minimal version 2020-05-26 22:12:10 +02:00
setup.cfg Allow list_unreleased_changes to format results at json & yaml formats 2020-07-07 19:07:25 +02:00 [Trivial] Remove executable privilege of 2016-05-09 16:38:37 +00:00
test-requirements.txt Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
tox.ini Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
watched_queries.yml Rename to 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00


OpenStack Releases


This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the website.

Changes to this repository are proposed using Gerrit at 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.