launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #06949
Re: Correct links for bug triage
On Fri, Apr 15, 2011 at 7:29 AM, Francis J. Lacoste
<francis.lacoste@xxxxxxxxxxxxx> wrote:
>
> On April 14, 2011, Robert Collins wrote:
>> > Unless you disagree, I'll update BugTriage and MaintenanceRotation
>> > schedule with my proposed link.
>>
>> I'm not sure if I agree or disagree :) - I think the key things are:
>> - every bug should be touched just enough to decide if its critical/high
>> - it should be easy to query or sort our triaged bugs
>> - our main web UI should not tell other folk we haven't been triaging
>> (and leaving a bug as e.g. 'high with status new' would leave a count
>> marker in the progress bar)
>>
>> I agree about with dropping INCOMPLETE_WITHOUT_RESPONSE which we can
>> do very easy from both searches... though I'll note that once we fix
>> bug expiry it will shrink that apparent backlog very quickly.
>>
>> What do you think?
>
> Well, incomplete bugs expire after 30 days, so it's still a long time to have
> dangling requests in our queue.
>
> I agree that removing INCOMPLETE_WITHOUT_RESPONSE is the thing to do from the
> queries. I'm still not sure that having to visit two links really pulls its
> weight.
I'd like to have one link that shows both, and call it 'Needs
triaged', replacing 'New' in the bug portlet, and then it would be
lovely :)
I think that needs a bit broader discussion though :)
-Rob
References