discussion of bug triage

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

discussion of bug triage

L. David Baron
We had a discussion of layout bug triage at our Layout/Graphics
meet-up in Paris.

The concerns I had that led to the discussion were:

 * I'm worried that in some cases we fail to get regressions triaged
   quickly, which is important both so that we don't ship them, and
   so that the person who wrote the patch that caused them still
   remembers the patch well.

 * I'm worried that we're duplicating effort in reading bugmail.

We didn't come to a whole lot of conclusions, but the one we did
reach is that one way we can acknowledge having read a bug and
noticed that it doesn't seem like any other immediate action is
needed is by setting the priority field.  This should probably use
the priorities as described in
http://dbaron.org/log/20090120-bug-priorities if we want to be
consistent, but that isn't even critical as the more important part
is having something approximate as an acknowledgment that the bug
has been looked at.  That said, other actions should be taken if
they are useful, such as marking dependencies, cc:ing or
needinfo?ing relevant people, or describing the code where the
problem is likely to be.

-David

--
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Cameron McCormack-4
L. David Baron wrote:
> We didn't come to a whole lot of conclusions, but the one we did
> reach is that one way we can acknowledge having read a bug and
> noticed that it doesn't seem like any other immediate action is
> needed is by setting the priority field.

http://mzl.la/1hluxB5 is a search for bugs that:

   * were created on the day of, or after, that discussion we had,
   * is in one of the Layout components,
   * are UNCONFIRMED, NEW or REOPENED,
   * do not have an assignee, and
   * do not have a priority.

We agreed to set the priority field if we triage a bug but have no other
information to contribute.  This means that if we make some other
changes to the bug, the lack of a priority value could still cause it to
appear in the search results.  So perhaps we can all attempt to set the
priority field even if we are making other changes to the untriaged bug,
unless the change would otherwise make the bug not appear in the list
(e.g. by resolving it, changing its component, etc.).
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Mats Palmgren-2
In reply to this post by L. David Baron
On 10/27/2013 10:55 PM, Cameron McCormack wrote:
 > L. David Baron wrote:
 >> We didn't come to a whole lot of conclusions, but the one we did
 >> reach is that one way we can acknowledge having read a bug and
 >> noticed that it doesn't seem like any other immediate action is
 >> needed is by setting the priority field.
 >
 > http://mzl.la/1hluxB5 is a search for bugs that:
 >
 >    * were created on the day of, or after, that discussion we had,
 >    * is in one of the Layout components,
 >    * are UNCONFIRMED, NEW or REOPENED,
 >    * do not have an assignee, and
 >    * do not have a priority.

Thanks, that's a great start.  There are a few additional components that
I would like to include in that list, namely:

CSS Parsing and Computation
Internationalization
MathML
Print Preview
Printing: Output
SVG

I have shared a named query "Layout-untriaged" that include those.
I've also created "Layout-untriaged-backlog" that queries the same
thing but before 2013-10-25.  You'll find them under "Preferences"->
"Saved Searches" for easy inclusion in your Bugzilla footer/dashboard.

/Mats

_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Cameron McCormack-4
Mats Palmgren wrote:

> Thanks, that's a great start. There are a few additional components that
> I would like to include in that list, namely:
>
> CSS Parsing and Computation
> Internationalization
> MathML
> Print Preview
> Printing: Output
> SVG
>
> I have shared a named query "Layout-untriaged" that include those.
> I've also created "Layout-untriaged-backlog" that queries the same
> thing but before 2013-10-25. You'll find them under "Preferences"->
> "Saved Searches" for easy inclusion in your Bugzilla footer/dashboard.

Thanks, it makes sense to include those components.  I did not know
about shared saved searches.  That's a much better way of sharing it
than with the link I gave -- and it can be updated too.
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Mats Palmgren-2
In reply to this post by L. David Baron
After a few days of triage I see a couple of issues:

1. new bugs filed by ourselves sometimes does not have a Priority or
    Assignee, causing unnecessary triage

Please try harder to fill in at least one of those fields when you
file a new bug.

2. requests for new features seems to pile up, examples:
    https://bugzilla.mozilla.org/show_bug.cgi?id=931495
    https://bugzilla.mozilla.org/show_bug.cgi?id=931206

The best I can think of is to mark such bugs Severity:enhancement and
ignore those in the Layout-untriaged query.  Prioritizing new features
and assigning resources seems like a separate activity from triaging
other incoming bugs.

Thoughts?


/Mats

_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Robert O'Callahan-3
On Fri, Nov 1, 2013 at 10:17 AM, Mats Palmgren <[hidden email]> wrote:

> After a few days of triage I see a couple of issues:
>
> 1. new bugs filed by ourselves sometimes does not have a Priority or
>    Assignee, causing unnecessary triage
>
> Please try harder to fill in at least one of those fields when you
> file a new bug.
>
> 2. requests for new features seems to pile up, examples:
>    https://bugzilla.mozilla.org/**show_bug.cgi?id=931495<https://bugzilla.mozilla.org/show_bug.cgi?id=931495>
>    https://bugzilla.mozilla.org/**show_bug.cgi?id=931206<https://bugzilla.mozilla.org/show_bug.cgi?id=931206>
>
> The best I can think of is to mark such bugs Severity:enhancement and
> ignore those in the Layout-untriaged query.  Prioritizing new features
> and assigning resources seems like a separate activity from triaging
> other incoming bugs.
>

I agree.

Rob
--
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
*
_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout
Reply | Threaded
Open this post in threaded view
|

Re: discussion of bug triage

Mats Palmgren-2
In reply to this post by Mats Palmgren-2
On 10/31/2013 11:09 PM, Robert O'Callahan wrote:

> On Fri, Nov 1, 2013 at 10:17 AM, Mats Palmgren <[hidden email]> wrote:
>
>> After a few days of triage I see a couple of issues:
>>
>> 1. new bugs filed by ourselves sometimes does not have a Priority or
>>     Assignee, causing unnecessary triage
>>
>> Please try harder to fill in at least one of those fields when you
>> file a new bug.
>>
>> 2. requests for new features seems to pile up, examples:
>>     https://bugzilla.mozilla.org/**show_bug.cgi?id=931495<https://bugzilla.mozilla.org/show_bug.cgi?id=931495>
>>     https://bugzilla.mozilla.org/**show_bug.cgi?id=931206<https://bugzilla.mozilla.org/show_bug.cgi?id=931206>
>>
>> The best I can think of is to mark such bugs Severity:enhancement and
>> ignore those in the Layout-untriaged query.  Prioritizing new features
>> and assigning resources seems like a separate activity from triaging
>> other incoming bugs.
>>
>
> I agree.
>
> Rob
>


OK, I have updated the Layout-untriaged queries(*) to ignore
Severity:enhancement.

/Mats


(*)
https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Layout-untriaged

https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Layout-untriaged-backlog

_______________________________________________
dev-tech-layout mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-layout