2e254433d7
If you wants to wait for a specific patch to make it to the release, someone from your team can -1 the patch to have it held, or update that patch with a different commit SHA. Patches with no response will be merged by Friday March 26. $ git log --oneline --no-merges 11.0.0..1c35c12 07c0f8b Bump eventlet requirement 2f9ad19 remove unicode from code b53f7d2 Avoid caching images when unshelving f32ea3f Use a separate doc requirements file 81c7cf6 rbd volume support c57ac7a Pick up InstanceMetadata changes 32a4603 hyperv: Configures chassis asset tags for VMs. e7021d2 Add Python3 wallaby unit tests 14dbf50 Update master for stable/victoria Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: I5169fe20a9cfaf2a6ff0977733b2c2efbf289d5f |
||
---|---|---|
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.