Release requests and history tracking
Go to file
2018-11-20 16:57:39 +00:00
deliverables Merge "release ldappool 2.4.0" 2018-11-20 16:57:39 +00:00
doc document policy on adding new deliverables 2018-11-06 11:35:01 -05:00
openstack_releases Switch back to publish-to-pypi 2018-11-02 19:41:36 +01:00
templates Update and replace http with https for doc links in releases doc 2017-08-09 14:10:09 +00:00
tools Update tooling to support cycle-with-rc model 2018-10-24 08:41:13 -05:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview Added .gitreview 2015-07-02 09:25:52 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Switch to "tox -e docs" 2018-11-05 20:58:02 +01:00
bindep.txt install the python3 version of launchpadlib 2018-06-21 16:28:06 -04:00
CONTRIBUTING.rst Base ladder content for CONTRIBUTING.rst 2018-03-22 16:10:28 +01: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 Remove duplicate packaging 2018-03-08 14:29:25 +11:00
setup.cfg Merge "add a script to examine the gerrit acls for issues" 2018-03-05 15:00:34 +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 "Don't quote {posargs} in tox.ini" 2018-10-21 05:30:16 +00:00
watched_queries.yml remove extra blank line in watched query output 2017-08-04 10:26:22 -04: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.