re: Determining answers to any or all of the above might require
multiple rounds of dialog, and some of them need to be understood in
sequence rather than in parallel. They also require very different
sets of expertise to determine.
Yes! We should set up systems and process and skills that encourage and
allow teams to "nuture" bugs, and get the answers to these questions.
Going into bug triage with the idea that primary and most important goal is
to get regression bugs "off the list", and to make (snap/quick) decisions
works against the process of finding important regressions, finding them
fast, and getting them fixed before we ship; which should be the main
reason we are doing all this work.
https://bugzilla.mozilla.org/show_bug.cgi?id=1249083 is an example. seems
too bizarre to be an important or widespread problem, so ->works for me.
almost left for dead. then resurrected and tied to an important problem
and fix. bugs can often linger in these early stages for quite some time
before progress can be made, but we need to keep revisiting and keep trying
for breakthroughs in the information the dbaron lists.
Once the diagnosis gets better, the problems become more clear, then the
fixes can progress; often with great speed.
Streamline bugzilla to do these things and constantly remind all
participants that this is what we are trying to do.
-chofmann
> There are a number of separate things we want to understand in a bug
> report, as I described in http://dbaron.org/log/20120816-bug-system :
>
> Understand description
> Do the developers or triagers reading the bug understand
> what the reporter is saying?
>
> Agree it's a bug
> Do the module owners or peers or other authority agree that
> the problem is a bug?
>
> Can reproduce
> Can others reproduce the problem described?
>
> Why it's important
> What makes this problem important or urgent to fix?
>
> How to fix
> What should be done to fix the problem?
>
>
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
