Release requests and history tracking
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Előd Illés a4ed2e94f4 Mark requirements' ocata branch as EOL
Since every project transitioned to End of Life already, requirements
should have tagged with EOL, too. This patch tags latest patch on
stable/ocata with ocata-eol and the branch can be deleted afterwards.

Change-Id: I197457d2160a1668013854bd390779dc3c2c9002
1 year ago
data Merge "Sync mistral team release liaisons" 1 year ago
deliverables Mark requirements' ocata branch as EOL 1 year ago
doc Fix links in releases.o.o footer 1 year ago
openstack_releases Mark Yoga as released 1 year ago
templates Remove unused RC templates 4 years ago
tools Remove tag argument usage from helper scripts 1 year ago
.gitignore Switch to stestr 5 years ago
.gitreview OpenDev Migration Patch 4 years ago
.stestr.conf Switch to stestr 5 years ago
.zuul.yaml Switch to victoria job template 3 years ago
CONTRIBUTING.rst Move release team ladder & infra into proper page 2 years ago
LICENSE Add top level LICENSE file 5 years ago
README.rst moving to OFTC 2 years ago
bindep.txt Cleanup bindep packages 3 years ago
requirements.txt Remove stable:follows-policy tag banner 1 year ago
setup.cfg List cycle's releases with process_auto_release 2 years ago [Trivial] Remove executable privilege of 7 years ago
test-requirements.txt Update to latest hacking for pep8 checks 3 years ago
tox.ini Pin setuptools for Yoga release 1 year ago
watched_queries.yml Rename to 4 years ago
yamllint.yml add linter rules for vertical whitespace 6 years ago


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 OFTC IRC <>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.