Release requests and history tracking
Go to file
2019-10-21 08:57:57 +00:00
data Mark Train as released 2019-10-15 08:42:02 -05:00
deliverables Merge "TripleO RC tags + stable/train branches" 2019-10-21 08:57:57 +00:00
doc Merge "Update release process for R-1 and R+0" 2019-10-16 15:43:57 +00:00
openstack_releases Mark Train as released 2019-10-15 08:42:02 -05:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Update lib release instructions for freeze 2019-09-19 16:04:06 -05: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 Add Python 3 Train unit tests 2019-07-19 14:43:41 -04: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 Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00: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 Merge "Add Python 3 Train unit tests" 2019-08-08 09:50:12 +00: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.