launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

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

On 11-01-06 10:19 AM, Curtis Hovey wrote:
> On Thu, 2011-01-06 at 09:24 -0500, Aaron Bentley wrote:
>> That said, the 'Triaged' status seems redundant to me.  Triage is the
>> process of determining the importance, so any bug whose importance is
>> not 'Unknown' can be considered triaged.
> 
> Triaged is indeed a process. Launchpad uses triaged to mean someone who
> speak for the project has confirmed the issue and has assessed the
> priority.

I hadn't seen it phrased that way before.  I have always thought
confirmed meant that the bug had been verified to exist, and, ideally,
reproduced.  But when I triage a bug, I'm not confirming it in that sense.

Does 'Confirmed' mean that we actually do consider this a bug, rather
than 'Invalid' or 'Won't fix'?

> The triaged status is reserved for project members, but anyone
> can set a bug to the confirmed status.

If 'Confirmed' means that it isn't 'Invalid' or 'Won't fix', why do we
permit non-members to set it?

> We could do away with the triaged status if Launchpad reported the
> combination of bugs confirmed by project members that have sensible
> status (not unknown or undecided).
> 
> https://bugs.launchpad.net/launchpad-project/+bugs?field.status:list=TRIAGED&field.importance:list=UNKNOWN&field.importance:list=UNDECIDED
> shows that there are 88 bugs that claim to be triaged, but we actually
> do not know if we need to fix them now, or when an opportunity presents
> itself.

I guess we should re-triage those.

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

iEYEARECAAYFAk0l4dUACgkQ0F+nu1YWqI2JmgCfXwL2HcgXwDy5XbhiJsZfLS0t
zHYAnRedynCsGY34r9SC6H/+p2/aGNz+
=/ORw
-----END PGP SIGNATURE-----