Subject: Re: What is a CRITICAL bug in send-pr
To: Frederick Bruckman <fredb@immanent.net>
From: Richard Earnshaw <rearnsha@arm.com>
List: current-users
Date: 06/18/2003 11:22:54
> The whole idea of having two dimensions to the severity is what's
> really wacky. A single scale with a few more slots in it would be
> nice. It would also give us a chance to review the old ones, as the
> filing use isn't necessarily the best one to assess the priority.

We don't have two dimensions to severity.  We have one dimension of 
severity and one of importance.  Be careful not to confuse the two, they 
are very different.

We should be using priorities to govern what must be fixed before a 
release is made, not necessarily severity.

R.

PS  It's often true that a critical bug is likely to be high priority, and 
a non-critical one of low priority, but that's not hard and fast.  Indeed 
if we triaged bugs properly as they came in, we could assess their 
priority to the project and ensure that important (to us) bugs were fixed 
before a release rather than languishing in the database untouched.