Go to file
Sean McGinnis 9231840e8a Handle deliverables with legacy teams
Errors were being thrown if a team was no longer found under governance.
We don't need to worry about that situation to get the deliverable
details.

Change-Id: Ib5459a0bd9521c296fa4f3d0743d20c1f2e5208a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-04-11 06:44:55 -05:00
2019-04-10 11:30:01 +00:00
2018-07-10 10:38:33 +07:00
2015-07-02 09:25:52 +00:00
2018-07-10 10:38:33 +07:00
2018-11-05 20:58:02 +01:00
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07: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.

Description
Release requests and history tracking
Readme 141 MiB
Languages
Python 89.1%
Shell 10.9%