Release requests and history tracking
Go to file
Dmitriy Rabotyagov 837f30bd65 Release OpenStack-Ansible Train
Change-Id: Idcfe721237b73d6ad5ffda3fd9cb8875826e09bc
2021-03-25 11:36:34 +02:00
data Adding a new email for release liaison to hberaud 2021-03-09 08:58:06 +01:00
deliverables Release OpenStack-Ansible Train 2021-03-25 11:36:34 +02:00
doc Merge "Standardize topics to use during series" 2021-03-25 08:57:41 +00:00
openstack_releases Merge "fix nits" 2021-03-16 09:18:29 +00:00
templates
tools Merge "Add delete option to list_eol_stale_branches.sh" 2021-03-08 11:25:40 +00:00
.gitignore
.gitreview
.stestr.conf
.zuul.yaml
bindep.txt
CONTRIBUTING.rst
LICENSE
README.rst
requirements.txt add reno semver-next to the list-changes output 2020-09-03 08:34:49 -04:00
setup.cfg Adding a tool to catch projects that missed branching 2021-03-03 13:51:12 +01:00
setup.py
test-requirements.txt
tox.ini
watched_queries.yml
yamllint.yml

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.