Hello, fellow Patch Pilots and Ubuntu community members,
This post serves as the official hand-off for the Patch Pilot Program for the 23.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)
This cycle has completed. Please head over here for the 24.04 cycle.
Weeded through open bugs with patches attached and closed very old reports which I felt comfortable closing
Important Context:
The sponsoring queue is in great shape right now, so I thought it would be useful to reduce the bugs with patches list, many of which were from Jaunty through Saucy. I only made a small dent it in.
Sadly, not much achieved this shift, as I’ve been interrupted several times for time-sensitive things (due to Feature Freeze tomorrow). The sponsorship queue is still in fairly good shape, with only a single actionable at the time of writing.
The only request from not-Canonical was for dracut. I was unsure how to handle the request for a delta in this package, and consulted @bdrung who explained and kindly agreed to handle that in his next upload.
documentation improvements would be a good use of pilot time, but that’s going to be hard to move forward in a structured way in ~4 hrs every 3 weeks. As the queue is functionally empty right now, we need a plan.
Hi, that bug report & patch was result of multiday interactive debugging of the issues we were seeing between zfs dkms & v6.5 unstable kernel builds. And since @arighi doesn’t have upload rights for that package he filed bug report for me to sponsor. Which i did in under an hour between meetings.
Given the window was so short, I am surprised this bubbled up on your patch-pilot queue. Is our patch-pilot queue really empty that something so recent and under a couple of hours long raised your attention? What could have @arighi or myself have done to indicate that said bug report & deb-diff do not require a patch-pilot or sponsor, since that was in progress anyway?
The sponsor process does suggest using an “in progress” state + self-assignment, and that would have been a clue that something was going on. It was unassigned when I started looking at it - and I agree, if I were in your position I would not have assumed it would have made it to the sponsor queue in that timespan.
Yes, the general queue was down to 1-2 items as of yesterday!
I flagged this as off-topic - it’s an important question but given the instructions in the original post, could we move it to a separate topic, please?
It looks like the Foundations bot auto-subscribed ~ubuntu-sponsors to it because a debdiff was attached. Perhaps a tag to stop it doing that, if that doesn’t exist already? For git-ubuntu based MPs, I don’t automatically add ~ubuntu-sponsors if a different reviewer is already nominated.
vim MP: MP LGTM, but the bug reference is missing from the changelog entry. Requested this change to Danilo, who addressed the request. Approved and uploaded.
Sponsored rsyslog merge. While there’s a newer version in Debian now, this version is a bug fix release and the new one is not entirely so it wouldn’t really fit FFe.
I used git-ubuntu prepare-upload args to sponsor the merges, so history should be preserved in the target branch!
rsyslog was handled in the past, discussed and unsubscribed sponsors.
openssh SRU which was not yet ready, reviewed, tested and recommended several changes
octavia-dashboard I was unclear if this would not need more to be ready and asked on the bug what I’d want. But then this was auto-subscribed and might not yet have meant to be ready.
Important context
There was no activity in IRC.
I ran a bit short due to unplanned meetings, but there wasn’t much more in the queue either (two more MPs of my team for which I can withstand the stares for not having them sponsored).
Looked over patches for r-cran-flextable, dipy, and pyfai. They all look fine to me. I don’t have upload permissions for any of them though so they’re still available for the next patch pilot.
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.