Release requests and history tracking
Go to file
Sean McGinnis b6ca269386
Switch to ruamel for yaml handling
The Ruamel library has better support for modifying YAML while keeping
things like comments. This updates our yamlutil module to use
ruamel.yaml instead of PyYAML.

Story: 2002908
Task: 22880

Change-Id: I4ac66c9e3e40780b588377c1dfe42511eed231a3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-07-08 11:40:11 -05:00
data Update placement release liaisons 2019-07-01 14:54:16 +01:00
deliverables Merge "neutron-fwaas rocky 13.0.2" 2019-07-08 10:37:09 +00:00
doc Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
openstack_releases Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
templates switch mailing lists to openstack-discuss 2018-12-04 10:41:28 -05:00
tools Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Revert "Increase tag-releases job timeout" 2019-04-16 14:13:40 +00:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Point to release-management info in governance 2018-11-01 16:09:48 +01:00
requirements.txt Switch to ruamel for yaml handling 2019-07-08 11:40:11 -05:00
setup.cfg Update Liaison Scripts 2019-06-19 16:22:29 -07:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Switch to stestr 2018-07-10 10:38:33 +07:00
tox.ini Add a 'generic' release-type. 2019-04-18 15:27:27 +10:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

Using This Repository

All official OpenStack software should go through the 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).

This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.

The repository is managed by the Release Management team.

image

Refer to the reference documentation for more details

Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.