With the new release identification / naming schema [1] (like: 2023.1 Antelope) new stable branch naming was introduced (like: stable/2023.1). This results a false warning message now when validating bobcat releases [2], as the validator searches for stable/antelope instead of stable/2023.1 stable branch. This patch fixes the validate_series_open validator to use release_id for the branch name, where that exists. Besides, the patch also refactors the release-id fetching and ensures that the release_id is always returened as string and the series name is used if there is no release_id for the given series. [1] https://governance.openstack.org/tc/reference/release-naming.html [2] validate_series_open: There is no stable/antelope branch defined in deliverables/antelope/<x>.yaml. Is the bobcat series open? Change-Id: I71eae27f124473699c22dac0b0eb2b0b1d44b4da
16 KiB
16 KiB