Go to file
Sean McGinnis 86a537ba23 Train final releases for cycle-with-rc projects
These are the final release taggings for all cycle-with-rc projects.
While not required, having PTLs ack this patch would be nice to include
that record in the merged metadata.

Since it always comes up - yes, the diff-start is right. That's the
calculated starting point where the last stable branch was created.

Change-Id: Icd4d3e6bc2bdd23b7073c38ea1a2e9100e679834
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-10-15 08:40:58 -05:00
2019-09-23 18:04:44 +02:00
2018-07-10 10:38:33 +07:00
2019-04-19 19:37:48 +00:00
2018-07-10 10:38:33 +07:00
2019-07-19 14:43:41 -04:00
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07:00
2019-08-08 09:50:12 +00: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 142 MiB
Languages
Python 89.1%
Shell 10.9%