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.
 
 
Zuul 2f920e8c28 Merge "Release hacking 4.1.0" 2 days ago
data Mark Wallaby as released 1 week ago
deliverables Merge "Release hacking 4.1.0" 2 days ago
doc Merge "[doc] Add release note landing page" 4 days ago
openstack_releases Mark Wallaby as released 1 week ago
templates Remove unused RC templates 2 years ago
tools Ignore trailing projects from RC1 4 weeks ago
.gitignore Switch to stestr 3 years ago
.gitreview OpenDev Migration Patch 2 years ago
.stestr.conf Switch to stestr 3 years ago
.zuul.yaml Switch to victoria job template 11 months ago
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2 years ago
LICENSE Add top level LICENSE file 3 years ago
README.rst Update README.rst for better looks 1 year ago
bindep.txt Cleanup bindep packages 1 year ago
requirements.txt add `reno semver-next` to the list-changes output 8 months ago
setup.cfg Adding a tool to catch projects that missed branching 2 months ago
setup.py tox setup 6 years ago
test-requirements.txt Update to latest hacking for pep8 checks 9 months ago
tox.ini Update to latest hacking for pep8 checks 9 months ago
watched_queries.yml Rename review.openstack.org to review.opendev.org 2 years ago
yamllint.yml add linter rules for vertical whitespace 4 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.