Release requests and history tracking
Go to file
Andrey Kurilin 93de96d9c9 Propose rally-openstack 1.6.0
Change-Id: I509a75508ccaac47a6dc3083875d85fc68bdc757
2019-11-29 09:30:38 +02:00
data Mark queens as extended maintainance 2019-11-19 09:27:49 +00:00
deliverables Propose rally-openstack 1.6.0 2019-11-29 09:30:38 +02:00
doc Merge "Update process for R+1 week" 2019-11-21 16:16:43 +00:00
openstack_releases Merge "Be explicit about python3 executable" 2019-10-24 09:34:46 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Fix ssh host addr link. 2019-11-20 18:16:54 +08: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 Merge "Skip jobs on data file only changes" 2019-11-15 01:00:20 +00:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04: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
requirements.txt Unpin keyring to unbork twine validate check 2019-11-19 10:11:52 +01:00
setup.cfg Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Switch to stestr 2018-07-10 10:38:33 +07:00
tox.ini Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 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

image

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.