Triage of changes on 2026-05-26

Nothing to report. All LP bugs under control or watched by the team, nothing on GH or Discourse, and the proposed queue should be triage-able soon.

2 Likes

Hello Renan,

I’ve periodically wandered over to Launchpad to glance thru recently added bugs, just out of curiosity and to get a sense of the pulse of things.

One question keeps coming to me every time I visit:

  • Why, why, why … SOOOO many bugs!

I don’t want to cast aspersions on the volunteers that do the development work, but that number of bugs (136237 being reported) just seems to suggest that the situation is SOOOO out of control!

Just wondering, has it been considered that dedicated teams be exclusively assigned to each “Category” of bug?

I realize that such an approach would take resources away from the most critical, but wouldn’t an improved code base resulting from fewer “minor” bugs would reduce resources spent constantly reviewing and reporting on those “easier to clean up” issues.

Just a thought coming from an outsider, along with well wishes for things to improve!

:slight_smile:

1 Like

Ubuntu is a big project, with dozens of thousands of source packages. There are different teams working on it, and this particular triage report is about the packages that the Server team maintains.

1 Like

Hi @ericmarceau - As Andreas said, there is a vast ocean of source packages out there. Different teams and different communities or even individual contributors have different priorities.

I want to make any reader aware that anything that is requested to come into the main component (default installed or of common use) has to pass the MIR process, which is a quality gate. As part of that, the owning team must subscribe to watch after bugs. Thereby chances someone looks after each bug in a controlled fashion are much higher in main, but details might still differ per team.

As @ahasenack mentioned these reports here are about the Server Team Triage in particular which follow the general triage guidance of the Ubuntu project but is probably the most defined set of actions and has a daily rotation to look into all the cases (launchpad, discourse and github). Those reports you see here existed for years, but up until recently have been on the mailing list.

Why, why, why … SOOOO many bugs!

You have to understand that triage is exactly that - triage. It closes issues that are wrong, it asks questions and marks as incomplete if there isn’t enough data, it classifies issues as OK but not important and finally marks those that we decide we have to prioritize and work on. The last set will be handled by us, the rest might get a look by community volunteers - but the influx is higher than the capacity and due to that the number increases. But those cases deemed important to be resolved and actionable are handled all the time.

And of those bugs many are “last updated long ago” or something else that makes them not invalid, but also not more actionable than in the past. Some teams regularly close all old cases, some don’t - this isn’t predefined by the project and by others considered rude. Therefore the number is huge, but should not be too concerning.

1 Like