Tony Breeds 1ea1c811b8 [winstackers] Create milestone-1 releases
This is a procedural review to create new releases for libraries following cycle-with-intermediary  model with code changes

Teams should update this change as appropriate

Change-Id: Icca2038e8370ec9a60c367b4a36ac6bf589522e9
2019-06-06 23:07:07 +10: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
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07:00
2019-04-18 15:27:27 +10: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.1%
Shell 10.9%