Go to file
Thierry Carrez a44831a407 Import history for independent QA deliverables
Rarely-released QA cycle-independent deliverables never had their
release history imported. This should be done so that they do not
show up in governance/release gap analysis.

Note that we skip the erroneous "v0.0.4" tag for karma-subunit-reporter
and will issue a fresh 0.0.5 in another review to clear up any
confusion.

Change-Id: I3b8a7221eed9ede4cd749f6d766d09a1f965c79e
2018-12-07 17:48:04 +01: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%