Hello fellow Patch Pilots and Ubuntu community members,
This post serves as the official hand-off for the Patch Pilot Program for the 26.10 cycle. The purpose of this thread is to ensure continuity in our program, keeping operations smooth and contributors supported. Whether you’ve just wrapped up a piloting session or are gearing up for your session, this space ensures that no detail gets lost in the shuffle. If you are interested in what is going on, you can subscribe to this post.
Please reserve responses in this thread ONLY to hand-off reports. If you have a question as a contributor please check with the current patch pilot. If you need a clarification from the last pilot please reach out to them separately. If you have a more general question please create a new topic in this category.
To the incoming pilot: please take a moment to review the updates from the previous session. It provides the context you’ll need to pick up where they left off. When writing your own report, please include the following headlines:
Notable Achievements
Important Context
Notable Contributors (tag them if you know their discourse username)
Program Improvements (anything that you think needs documenting or otherwise improving)
Sponsoring report had a hard time loading, so I went through this view instead. It turned out that my Firefox played a trick on me again because of sponsoring reports not being available on httpS
Claimed review slot for old stuff already finished:
znc openssl 4 ftbfs: upstream PR has unaddressed comments that may change this patch. I commented on our PR, and abstained from the review so it remains in the review queue.
ubuntu-release-upgrader (~shemgp, #504125) — Needs Resubmitting: merge conflicts; submitted against wrong repo (+source/ubuntu-release-upgrader vs actual ubuntu-release-upgrader git).
linux-raspi (~udyr666, #504173) — Disapprove: kernel patches must go via the kernel-team submission procedure.
wvdial (~amorris953, #504343) — Needs Resubmitting: rebase against 1.61-9 and stonking; consider ubuntu/resolute-devel for SRU and follow the SRU template.
These were open against resolute, and are now outdated. Reviewed as needs-resubmitting if these should go to stonking now, and questioned if it should be SRUed to resolute.
These were already uploaded, but the MPs were not marked as merged for $reasons. I asked the owners to mark them as merged for these to disappear from the sponsoring report.
Glad to see the sponsoring report working on httpS this time!
Launchpad was in such a pain this afternoon that it left a lot of room for being Mattermost-pinged and side-tracked.
I still had some look at both ends of the queue. Old stuff is usually not directly actionable, that’s why I also looked at newest stuff.
Please reserve responses in this thread ONLY to hand-off reports. If you have a question as a contributor please check with the current patch pilot. If you need a clarification from the last pilot please reach out to them separately. If you have a more general question please create a new topic in this category.
)
