Conversation
Looking at the ISO tracker[1] for comparison, I noticed something strange for Ubuntu Desktop arm64. The serial is from the 08 there. Browsing in the folders, that's because all images are copied to the next day before being overridden by a newer build, meaning latest serial folder for Ubuntu Desktop is 20251209, but that folder still has an arm64 build from 08. That machinery is extremely confusing and error-prone 😢 [1]: https://iso.qa.ubuntu.com/qatracker/milestones/476/builds
utkarsh2102
approved these changes
Dec 11, 2025
Member
utkarsh2102
left a comment
utkarsh2102
left a comment
There was a problem hiding this comment.
This is already a good improvement. Just a small nit below.
Comment on lines
+1
to
+3
| milestone: | ||
| name: Snapshot 2 | ||
| slug: snapshot-2 |
Member
There was a problem hiding this comment.
I was thinking this can go in the python script as an additional parameter, no?
Now that we have data.yml, we can use -m to pass the milestone slug?
So something like this: ./publish-image-set -d resolute-snapshot-2.yaml -m "snapshot-2"
Collaborator
Author
There was a problem hiding this comment.
idk, why not, but also not bringing much value as of now, and it spreads the data appart. What I'd like is to be able to quickly tell the input data we need to do a release, and that YAML file currently does that, but not anymore if we need to pass a name on the CLI
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
2 participants
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.
See each individual commits for some history and Gemini madness.
Regarding the release, here is the script for Questing Snapshot 2:
And here is the script for Resolute Snapshot 2:
Here is an extract of the word-diff between the two:
[...] {+# kubuntu-amd64+} ARCHES='amd64' for-project [-ubuntu-unity-]{+kubuntu+} publish-release daily-live [-20250624-]{+20251209+} desktop named snapshot-2 {+# lubuntu-amd64+} ARCHES='amd64' for-project [-ubuntucinnamon-]{+lubuntu+} publish-release daily-live [-20250624-]{+20251208+} desktop named snapshot-2 {+# ubuntu-desktop-amd64+} ARCHES='amd64' for-project [-ubuntu-budgie-]{+ubuntu+} publish-release daily-live [-20250624-]{+20251209+} desktop named snapshot-2 [...]We can see that the produced commands are alike, even for Ubuntu Desktop, so it should be fine to run.
In terms of retrospective on this process: