← Back to team overview

launchpad-dev team mailing list archive

Re: Critical bugs over a month old still critical?

 

On 19 August 2011 21:12, Francis J. Lacoste
<francis.lacoste@xxxxxxxxxxxxx> wrote:
> On 11-08-19 03:31 PM, Aaron Bentley wrote:
>>> > One source of confusion here is the "critical" name.
>> Let's change the critical name, then.  It's not just confusing to us,
>> it's misleading to outsiders who look at our bug lists.  We're not using
>> Medium, so let's move our High bugs to Medium, our Critical bugs to
>> High, and reserve critical for things that actually are critical.  (And
>> update our policies accordingly)
>
> Like I said in the past, I'm not opposed to this. If I recall correctly,
> I thought at the time that the issue would be moot in a couple of
> months, and that was the main reason not to do it. Seems like the issue
> isn't moot.
>
> If a lot of people think it would make the situation clearer, then let's
> do this.

+1

(As an aside, I wonder if this problem is most acute for native
English speakers? As you've seen, I have trouble untangling the
language meaning of critical from the token just-a-bucket meaning
we've been using in Launchpad.)

[...]
> We need to investigate that stream of incoming rework and stop it at
> the source if we ever hope to burn these issues down. Once I sort
> out the recruitment projects I'm working on, that's my next project.

Awesome, that's great to hear.


References