1f357b54e3
Teams with distributed leadership type have release liaisons listed in governance repository's projects.yaml file instead of a single PTL. This was introduced in the check_approval.py script, but it did not work (though we did not realise this as usually releases repository's release_liaisons.yaml also contains the release liaisons). This patch fixes the check for distributed leadership type. Change-Id: I93fbf2be0f0da85dedfe9b9f8d5876ca5b9e4b2e
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.