Go to file
Doug Hellmann 510e8c9a5d add a script to get a list of unreleased changes for a team
Change-Id: I061cea61dd5d0a7711faae9e06809993caf36de9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-11-19 12:57:18 -05: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-03-08 14:29:25 +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 140 MiB
Languages
Python 89%
Shell 11%