release.py: run source jobs from newest distro - #1537
Draft
scpeters wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prototype of suggestion in #1536 (comment)
As noted in #1536 (comment), the gz-tools2-source failed because it was executed on
focal, the oldest distro with debian metadata defined in gz-tools2-release that is also end-of-life (EOL). @azeey suggested that we could delete the EOL metadata, and I agree that we can, but I think we can also change the release.py logic to use the last discovered distro in the list, instead of the first, which may correspond to the newest distro when the distros are sorted in the correct order. For now, I've ensured that they are sorted in alphabetical order, which will work until the next release after Ubuntu Z.