
This release picks up new commits to cinder since the last release from stable/ussuri. This is being proposed as a convenience to help make sure stable changes are being released. If the team is good with this going out, please respond with a +1 to let the release team know it is OK to proceed. If it is not wanted at this time, or if there are more changes that would be good to get merged before doing a stable release, please leave a -1 with a comment with what the team would prefer. We can then either abandon this patch, or wait for an update with a new commit hash to use instead. $ git log --oneline --no-merges 16.3.0..62da20185 35d56b680 Fix typo in Dell EMC Unity driver documentation f6d7b0919 Open local image files with "rb" mode e156653d3 Fix sporadic cleanup unit test failure dc8a1beab Label temporary files created by image_utils d9c029c17 Add ports filtering support to Dell EMC XtremIO driver ba8d19822 Tests: Don't assert notifier not called 34120d498 Backup manager: Synchronously call remove_export 610b59b27 Add support for RBD fast-diff feature for backups stored in Ceph b32a0f0cf Drop lower-constraints job d5fed21fd API validation: Add cinder_host type to support ipv6 in manage 1aa907300 Pure: Add default value to pure_host_personality 849fb4f19 [Pure] Fix failing consistency group tempest tests Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: I61ef6a5099eca7d92b85b1b15e465f8225e13401
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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.