Launchpad falsely claims distribution Importance == package Importance

Bug #253380 reported by Matthew Paul Thomas
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Undecided
Unassigned

Bug Description

In Ubuntu, a bug reported about a package in Universe may be of critical importance for people who have installed that package, but of low importance for Ubuntu as a whole, because hardly anyone installs the package. Unfortunately, Launchpad requires these two to be represented by a single Importance value.

This is causing difficulty for the QA team: either release management is made more difficult because bugs are marked Critical or High when they are not important for an Ubuntu release, or QA is made difficult for rarely-used packages because they are only ever allowed to use Low importance (or Low and Medium, depending on the package).

This could be fixed by letting bugs have a separate Importance value for the distribution as a whole, and for individual packages in that distribution.

Tags: lp-bugs
description: updated
Revision history for this message
Christian Reis (kiko) wrote :

I think this is actually a wontfix. If the bug is critical in universe, then it has to fit into the definition of critical -- and a bug in a package which is broken for only a very few people is probably not one.

It seems to me that you're suggesting that the collective of bugs ordered by importance is actually split into two separate groups: main and universe. I would agree with that, but suggest that fixing that is done by allowing people to view those groups separately, not by adding more knobs to twist.

I don't really understand "low importance for Ubuntu as a whole" -- universe and main are both Ubuntu proper.

Changed in malone:
status: New → Won't Fix
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I'm sorry I mentioned "Universe" in my example; it seems to have been thoroughly misleading. I did not suggest anything about two separate groups. My point was, even a crasher bug in a rarely-installed Ubuntu package will be less important *for an Ubuntu release* than a bug in a commonly-installed package.

The Ubuntu QA team are on the verge of disagreeing with you that "a bug in a package which is broken for only a very few people is probably not [Critical]", which is why I reported this bug. They discussed this on the ubuntu-devel@ mailing list last month <https://lists.ubuntu.com/archives/ubuntu-devel/2008-June/thread.html#25666>, and again in their meeting yesterday <https://wiki.ubuntu.com/MeetingLogs/QATeam/20080730>, and they appear to be about to decide that Importance should be decided relative to the package rather than relative to the distribution. This would make handling bugs easier for individual packages, but it would make Importance useless for Ubuntu release management.

I don't think they should have to make this choice. I think Importance should be useful for Ubuntu release management, but if so, we need to fix Launchpad so that it is. Otherwise, if we agree that Importance for a bug in a package should be decided relative to the package only, then <https://bugs.launchpad.net/ubuntu> should no longer link to or count the Critical bugs in Ubuntu as a whole, because that will no longer be a meaningful list.

Changed in malone:
status: Won't Fix → New
Revision history for this message
Curtis Hovey (sinzui) wrote :

I am makring this as wont fix because the correct solution is bug heat, which recongnises orgin and subscrptions.

Changed in malone:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.