launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-08-19 03:02 PM, Francis J. Lacoste wrote:
> On 11-08-19 07:40 AM, Gavin Panella wrote:
>> The Red Squad is going to be coming off a long hard feature cycle
>> soon. I'm looking forward to maintenance, because I want to have time
>> for longpoll and the SOA stuff. However, the Critical bug list is
>> huge, and I have a sinking feeling that I won't have time for those
>> things. I want to see if I can move the goalposts.
>>
> 
> On to your original question though, my answer is 'yes', they are still
> 'Critical'. The time it takes to fix issue isn't related to their
> priority. The fact that we cannot close all our "critical" issues in a
> month doesn't make them less of a priority.

No, but for "critical", in the normal sense, it is unacceptable to have
not fixed it within a month.  You should be working day and night until
it is fixed, and if you usually don't fix your critical issues within a
month, your web application won't be viable very long.

So the fact that your application is still viable, despite having not
fixed the bug after a month, is a strong indication that the bug wasn't
critical in the normal sense.

> 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)

> Think of it as 'Work-on-first' bucket which is what they are about.

And since Critical doesn't mean "must be fixed now" why is it a
work-on-first bucket?  Why do we have a focus on burning it down to
zero, at the cost of stalling our high and low bugs?  It seems like
allowing us to fix high bugs could improve the overall user experience more.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5OuhIACgkQ0F+nu1YWqI3EAQCfduBGnCpjfCTCROlCrAtx6LSv
BDwAoIG0VEm8ZHk+DEf8b8k19QcId/d3
=D8r3
-----END PGP SIGNATURE-----