Go to file
Gorka Eguileor 7af37cd370 Move cinderlib to cycle-trailing
Cinderlib was added late in the Stein cycle, so it went in with the
independent release model, but the appropriate model is cycle-trailing.

Cinderlib is different from other OpenStack libraries.  It provides an
object oriented abstraction of the Cinder drivers for the purpose of
consuming them outside of OpenStack.  Using the Cinder drivers means
that it has the Cinder project as a dependency and needs it to be
released before the cinderlib release. This is why the cycle-trailing
release model is the most appropriate.

This patch adds cinderlib to the Train release as a cycle-trailing
project.

Change-Id: I4bc7068e2ac41af2b879d382e73cfd16e6f2927c
2019-04-22 10:18:04 +02:00
2019-04-10 11:30:01 +00: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 141 MiB
Languages
Python 89.1%
Shell 10.9%