Chris Dent abdd97aaef Cycle-highlights for placement
There's not a lot to report because the vast majority of time was
spent on the first item in the list.

Doing this separately from the actual release as this is ready
but the release is not (some critical docs remain).

Change-Id: I1a4ce54559268dc7640345b3f8d302c6140e80cf
2019-03-17 23:01:10 +00:00
2019-03-14 17:50:22 +01:00
2019-03-12 20:06:17 +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 132 MiB
Languages
Python 89.2%
Shell 10.8%