Release requests and history tracking
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Sean McGinnis f54b1a1a63
stevedore 3.0.0
10 hours ago
data Merge "Remove congress deliverables from Victoria release" 3 weeks ago
deliverables stevedore 3.0.0 10 hours ago
doc Test bugfix branching with release-test 1 week ago
openstack_releases Allow list_unreleased_changes to format results at json & yaml formats 3 days ago
templates Remove unused RC templates 9 months ago
tools Merge "Allow list_unreleased_changes to format results at json & yaml formats" 13 hours ago
.gitignore Switch to stestr 2 years ago
.gitreview OpenDev Migration Patch 1 year ago
.stestr.conf Switch to stestr 2 years ago
.zuul.yaml Switch to victoria job template 1 month ago
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 1 year ago
LICENSE Add top level LICENSE file 1 year ago
README.rst Update README.rst for better looks 8 months ago
bindep.txt Cleanup bindep packages 3 months ago
requirements.txt Cap jsonschema 3.2.0 as the minimal version 1 month ago
setup.cfg Allow list_unreleased_changes to format results at json & yaml formats 3 days ago
setup.py tox setup 5 years ago
test-requirements.txt Update docs building, Python 3 cleanup 2 months ago
tox.ini Install wheel in validate venv 2 months ago
watched_queries.yml Rename review.openstack.org to review.opendev.org 1 year ago
yamllint.yml add linter rules for vertical whitespace 2 years ago

README.rst

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.