f32b877ece
All releases are announced to the release-announce ML, except Release candidates, which were still sent to openstack-discuss. The rationale was that RCs should be announced to a developers list rather than a downstream consumers list, so that they trigger testing. But that is less true now that there is a single -discuss list, where they generate a lot of noise around RC1, without triggering any additional testing. They also confuse some downstream consumers which expect those to go to the usual release announce list. This patch removes the exception and makes sure we send all RC announces to the release-announce list. Change-Id: Id33dba37b4d53962a2170ec401499fe3dd2e24bf
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.