openstack/releases
Code Issues Proposed changes
Release requests and history tracking
16,034 Commits 1 Branch 0 Tags 129 MiB
Python 89.1%
Shell 10.9%
47e945c28b
Go to file
Sean McGinnis 47e945c28b
Branch karbor for victoria 
This adds the missing stable/victoria branch for karbor.

Change-Id: I53f90807ba4e42908453b5bf915e217027b1e889
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-10-02 15:30:02 -05:00
data Fix release liaison email typo 2020-09-08 16:57:06 -05:00
deliverables Branch karbor for victoria 2020-10-02 15:30:02 -05:00
doc Merge "Update SKS Keyserver URLs" 2020-09-28 15:03:02 +00:00
openstack_releases add reno semver-next to the list-changes output 2020-09-03 08:34:49 -04:00
templates
tools Add script to semi-automate bulk releases 2020-09-11 14:48:55 -05:00
.gitignore
.gitreview
.stestr.conf
.zuul.yaml Switch to victoria job template 2020-06-02 14:28:30 -05:00
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05:00
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 Allow list_unreleased_changes to format results at json & yaml formats 2020-07-07 19:07:25 +02:00
setup.py
test-requirements.txt Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
tox.ini Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
watched_queries.yml
yamllint.yml

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.