27d4f7db98
This updates the script to not require a specific topic to make it easier to automate a job that periodically makes sure all open reviews have had the PTL and liaison added. Also refactored the adding of teams because bash array handling can be a bit wonky sometimes and not always append values. This makes sure no teams are skipped. This is slightly less optimized for large reviews like the final series release since it loops through teams based on the deliverable files. As a slight optimization, it will skip a team if it was the same team as the last deliverable file. It just might be possible that the same team will be processed multiple times if their deliverable files are not in alphabetical order, but there is no harm in that other than taking slightly longer to complete. Change-Id: I9a9194ea276aa0120aef21a321f48a93419fb848 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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.