828e285701
We use release-types as a way to verify that versions are compatible and if needed reflected accurately in the code (puppet, xstatic). If one isn't set explicitly then we assume python-service. In certain circumstances (anything other than the first release in a series) we also perform python specific requirements checking on all 'python' types. Add a new 'generic' type that uses the same rules to validate version numbers but wont run any python specific checks. We need this a projects (like monasca-thresh) will fail the requirements check for 2nd or greater releases[1]. An alternate would be to have the requirements code check if setup.py exists before calling it but that seems like the wrong layer to me. [1] http://logs.openstack.org/54/652854/1/check/openstack-tox-validate/80df01c/job-output.txt.gz#_2019-04-16_06_08_00_636538 Change-Id: I3fcde5eb266f954fddb6871ce8690b93b8fd7a8d
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.