52323de498
The placement team decided that os-resource-classes should follow an independent release cycle as it eases various aspects of integration with the multiple projects that consume the package and the fact that the package is simply a big enumeration of symbols pointing to strings. The expectation is that henceforth there will be a new release each time there is one or more new symbols available. Change-Id: I6349fe9eaa65fe871f3ed13c8b066115c9a035c3
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.
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.