Ghanshyam Mann 212f23ca69 Create stable/train for devstack
This commit cut the train branch for devstack

Next step will be on devstack side to complete
the step#7 onwards mentioned in https://releases.openstack.org/reference/process.html#rc1-week

Change-Id: Ic89c4e6b520c0f0a3cb8cb8d3d3244a187824242
2019-10-04 14:43:54 +00:00
2019-09-23 17:08:26 +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 132 MiB
Languages
Python 89.2%
Shell 10.8%