59953f787a
Deliverables following the cycle-with-intermediary model are expected to release multiple times throughout the development cycle. Since networking-baremetal only released once last cycle, and has not done a release yet this cycle, this proposes changing the release model to cycle-with-rc so the expectation is only that it will release an RC by the end of the cycle prior to doing the final release. This is just a suggestion for the team to consider. The important point is past the milestone-2 point, downstream planning starts happening for what will be included in the release. We just want to try to avoid the situation where downstream expects something to be included, but we need to unexpectedly drop it from the coordinated release late in the cycle. For the team, please respond to this patch in one of the following ways: * -1 this patch and follow up with an intermediary release * +1 this patch and we will switch over the release model * -1 this patch, but acknowledge a release will be done prior to the RC1 deadline. Change-Id: I3467602aeeb80979a16cc10a8eeb788fbbad98c5 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
|---|---|---|
| data | ||
| deliverables | ||
| doc | ||
| openstack_releases | ||
| templates | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| watched_queries.yml | ||
| yamllint.yml | ||
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack 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).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.