Severity / priority project: the home stretch

[Dave Jones]

On Thu, Jul 02, 2009 at 08:06:06PM +0100, Adam Williamson wrote:
 
 > Talking about use, I will soon send out a review of bugs open on Rawhide
 > and marked 'critical' severity. I'd like to have a review of this set of
 > bugs each week. I don't necessarily want to be the one doing it,
 > however. :) It'd be an ideal project for a community member: it's quite
 > straightforward and requires no secret sauce, all you have to do is take
 > a quick look at a saved query each week, do some copy/paste-ing, and
 > pontificate. :) Let me know if you'd be interested in doing this.
 > 
 > We'll also be reviewing all 'critical' bugs (and, if we get ambitious,
 > even 'high' bugs in key components) during the blocker bug review
 > meetings for F12, and the triage metric system will probably use the
 > severity ratings for some metrics too.

For the kernel, I'm tempted to just mass-clear all the severity tags,
because as I mentioned before you embarked on this project, they are
utterly meaningless.

Case in point: http://is.gd/1mTt5

Asides from making the buglist look so unreadable I can't read it
for more than a few minutes without getting irritated, a quick skim shows
the main problem. People think a suspend/resume failure is urgent.
Or that their DVD writer can't write discs. Or that their sound card
doesn't play sounds. Or just about anything imaginable.

That this field remains user settable makes it a complete disaster.

	Dave