8bff71325a
This proposed a release for python-tackerclient to get any final merged changes out prior to the lib freeze for Wallaby going into effect. If the team is ready to proceed, please leave a +1 to acknowledge this release and we will process right away. If the team is working on any final merges, leave a -1 with some detail on the status and update the patch with the new commit hash to use when ready. Patches with no response will be merged by Monday, March 11. $ git log --oneline --no-merges 1.5.0..4e6dc4c 4e6dc4c CLI for Individual VNF LCM Operation Occurrence 6b29bb7 Support CLI for Getting List of VNF LCM Operation Occurrences 1299e15 Support of Retry VNF command in openstackclient cfe1411 Support CLI of Change External VNF Connectivity 5816753 Support of Fail VNF command in openstackclient e7a0c96 Fix error message for nonexistent vnf package 68df829 Dropping explicit unicode literal 17f4bca Fix old links in installation guide 69d9668 Update TOX_CONSTRAINTS_FILE Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: I84ada4201cd05b2d65c8c28d5cb7208f7700e038
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.