Plucky Puffin (25.04) Release Status Tracking

As we enter the final stretch of Plucky Puffin release cycle, the release team is working toward planned release date this Thursday, April 17th. We will use this thread as a live document to capture progress, blocking issues and next steps. While this document provides a high level status update, more granular details on the work being done can be accessed below with the Checklist

As we’re trying to be more transparent throughout the release process, it is important for us to know if this post and helpful, let us know what you find most useful or what is missing in a comment below.

Status - On Track

Tuesday April 15th

What happened last night ?
The plan was for @utkarsh to build our images but we had to wait for qt6base to migrate as it is used on multiple flavors. Thanks for @mwhudson who helped pushing them trough the finish line, we were able to start building after midnight. Unfortunately we faced some infrastructure challenges, in particular with our amd64 images.

Other Updates

  • we’ll keep watching zsync status and since it is seeded in only two images, if we can respin on time we will.
  • There was a request to sync distro-info-data given the new release name was available, but since this isn’t a bug fix, we will stick to our usual process and take care of it on opening and SRU To older releases. @paelzer to friendly reject.
  • Alsa (LP: #2106394, LP: #2100732, LP: #2106464) - adding some changes too late and because it is seeded in Desktop, this would cause too many image respin. We will not be accept it in the release, keep it unapproved and deal with it as SRU
  • 2024-qt - Dropped from the milestone and updated the bug with an explanation
  • Kernel RISC-V build restarted again as it was broken
    • LP team acknowledged the issue and prepped special builders that do not recycle at the end to have a chance to debug what is going on
    • Still the builds are so delayed we no more expect them to make it

Today’s Plan

  • Send out request for testing for non-amd64 architectures
  • cleanup and troubleshoot cdimage amd64 images and respin amd64 images
  • Prepare release announcement and review content with flavor leads

EOD Report

  • issues with LaunchPad have been causing delays with amd64 builds and publishing in general
    • Those have been resolved
    • By now all images have been pushed except desktop amd64
    • Images will have to be respun due to an issue with curtin requiring subiquity and desktop provision snap to be rebuilt
  • Kernel riscv builds still haunted and had an unplanned restart
    • Therefore despite the respin we do not expect that to be there
    • Regular updates of the Kernel will catch that over time
  • Discussed which images we’d respin
    • Only those with an installer, which means not preinstalled risc, preinstalled rpi, any cloud-images
  • The fix for Zsync has built and migrate right now, related images seeding it will be respun once published
  • We re-evaluated -unapproved and communicated how we’ll handle the cases there, some rejects some kept to become SRUs

Monday April 14th

Release Tasks today will include:

  • Produce Full set of images
  • Clear the NBS List
  • Bug reviews

EOD Report

  • @utkarsh requested Release Note Updates from relevant teams with missing content
  • Builds of the newest kernel on RISC-V are delayed but a fallback plan has been agreed on
  • We discussed topic of delegation Feature Freeze for flavors, @utkarsh to post a proposal soon
  • Established final source freeze
  • Disabled daily builds
  • Clear various queues for plucky (NBS, …)
  • Working with web team to make sure everything is ready for release day
  • Got a Release Name for 25.10 : Questing Quokka :tada:
  • Waiting on basefiles to migrate so we can build new images so that people can start testing
  • reviewed milestone bug list
    • Reverting zsync from 0.6.2-7 upload into to 0.6.2-7ubuntu1
  • Preliminary ISO testing and Infrastructure check
  • Now everything revolves around getting new images, Utkarsh Gupta to start building images before EOD
  • We also discussed WSL image options and decided to release interim images without support as it still allows use to exercise the process and testing.

Bugs to watch

https://launchpad.net/ubuntu/+milestone/ubuntu-25.04

Release checklist

Release team is hard at work closing all the items on the release checklist below:
https://warthogs.atlassian.net/browse/RTMP-2334

ISO Tracker

https://iso.qa.ubuntu.com/qatracker/milestones/467/builds

Staying in touch

Feel free to contact us on https://matrix.to/#/#release:ubuntu.com or comment on this thread if you think something need the release team’s attention.

14 Likes

In less serious context, we are happy to have Utkarsh hobbling to London to drive this with us. Perfect chance for me to steal his lunch today, as he could not catch up. Best wishes to his foot to soon be release with all fixes applied.

6 Likes

Wednesday April 16th Update

What happened last night ?

  • @utkarsh re-spin images after zsync migrated (lubuntu and budgie)
  • Until midnight server images were still being built because RISC-V is slow. it took about 6 hours for RISC-V to complete. Images are now complete.
  • A potential bug was brought up in cinamon flavor with casper but we decided it was a really cosmetic issue and should not warrant re-spinning all images.
  • calamares upload was accepted at 4am. There’s still something wrong about it in the proposed pocket but this should be unblocked soon.
  • @paelzer this morning looking into something Bug #2107402 “lsblk on IBM z Systems blocked by apparmor in 25.0...” : Bugs : util-linux package : Ubuntu
    • This problem breaks things on s390x but doesn’t impact installer environment which explains why we didn’t catch it earlier. apparmor profile are not installed in enforced mode in the installer environment.
    • Issue is easily worked around and has been release noted
    • It further shown related issues that will also be SRU fixed
    • Decision is to fix this problem as a SRU, release note it
    • We will also look deeper with @dbungert in to why apparmor profiles are not enforced in the installer environment
  • Release is progressing as planned with more testing until publishing can start.

End Of Day Update

  • libvirt → SRU + release note known issue (done)
  • apparmor kills s390x → SRU + release note known issue (done)
  • Riscv preinstalled not working → false positive, documented
  • respin for due to calamaris landing, triggered for kubuntu, lubuntu, unity
  • Demo of the web part expected in ~0 minutes (in staging)
  • Automated testing on images we already have is green
  • Manual tests come in being submitted
  • Tracked Desktop, about to ready but waiting for a crashdump test
  • Started “Questing Quokka” opening
  • Raspberry Pi testing with @r41k0u and @waveform Thanks!
    • Startup sound missing ? - not a blocker (@jibel : actually was removed intentionally)
  • ISO tracker getting load issues, @hyask to investigate with IS
  • Verified: In response to the keystore question on upgrade - the keystore is fine, do-release-upgrade to plucky continues to do zfs encrypted.
  • However, during release upgrade, LP: #2107408 was encountered. Subiquity may need to take a lesson here about mount order from Ubiquity (x-systemd.after= also works). Will need fixed in Subiquity, and a fix for existing systems somewhere else (grub2 postinst until 26.10?)

ISO Testing Status

  • Desktop arm64 - @tobhe
  • Desktop Raspberry PI
    • do a few more, but by the tests done already confidence is fine and will not stop it.
  • Sever Subiquity Arm64 largemem
    • While this was tested during the Beta, We need to identify resoure to do this again, Looking into possible cloud instance
  • s390x/ppc testing mostly done and rest ongoing
5 Likes

:tada: Happy Release Day :tada:

What happened since yesterday ?

  • The calamares issue was resolved, well tested and uploaded \o/ well done!!
  • lubunut/kubuntu/unity have been respun this morning and test began
  • Call for testing was repeated
  • We encountered an issue with the Iso tracker Database this morning with entries without product ID being set. Code has been tuned up to ignore them for now
  • Coordinated to ensure IS support to be available during the final hour of the release this afternoon
  • Established all source block

Today

  • Pre-publish
  • @paride follows up with image owners to be tested
    • @tobhe to look at server on laptop
    • Frank: all tested, missing the green light
    • Someone to test Unity if community can’t do it
  • We went through the checklist to ensure everyone knows what their tasks are today

Happy Plucky Puffin day!

8 Likes