Release requests and history tracking

Go to file

Sean McGinnis 692c88c200 Transition Tricircle to Queens EM Change-Id: Ic0bb406deaf130229fe473d573668a957807e84c Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>		2019-10-25 07:42:23 -05:00
data	Add Mark Goddard as an ironic release liaison	2019-10-23 06:58:33 -07:00
deliverables	Transition Tricircle to Queens EM	2019-10-25 07:42:23 -05:00
doc	Merge "Add note to highlights page explaining content"	2019-10-24 09:31:48 +00:00
openstack_releases	Merge "Be explicit about python3 executable"	2019-10-24 09:34:46 +00:00
templates	Remove unused RC templates	2019-09-23 18:04:44 +02:00
tools	Be explicit about python3 executable	2019-10-16 09:45:29 -05:00
.gitignore
.gitreview
.stestr.conf
.zuul.yaml	Revert "Increase tag-releases timeout"	2019-10-24 12:44:33 +02:00
bindep.txt
CONTRIBUTING.rst
LICENSE
README.rst
requirements.txt
setup.cfg	Merge "Add Python 3 Train unit tests"	2019-08-08 09:50:12 +00:00
setup.py
test-requirements.txt
tox.ini	Merge "Add Python 3 Train unit tests"	2019-08-08 09:50:12 +00:00
watched_queries.yml
yamllint.yml

README.rst

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.

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.