Improving the Bugzilla Triage Process for Extensions
Clint Talbert
I apologize for not cross-posting, as I didn't know that this newsgroup
existed. I'd love to get some AMO eyes on this thread:
http://groups.google.com/group/mozilla.dev.quality/browse_thread/thread/d08a7eeb4203651e#
In short this is what I propose:
This is mostly a Firefox problem, but I think that it could apply to any
Mozilla product that uses AddOns.
We often get users reporting errors into Firefox bugzilla components
that turn out to be caused by specific add-ons. The current triage
process is that once we determine that it is an extension problem, we
advise the reporter to notify the extension developer and we close the
bug report as "INVALID" (aka, not a Firefox bug).
There are problems with this:
* We have no way to know if the extension developer is ever actually
notified.
* An interested extension developer (or AMO reviewer) has no means to
query for these bugs and find them as they are scattered across Firefox
components and its never intuitive that you'd want to query for
"invalid" bugs.
So I propose we modify the QA triage process as follows:
* Once a bug is deemed to be caused by extension X, we:
** move the bug to Firefox->Extension Compatibility component
** Leave the bug in the "NEW" state (is this a good idea?)
** Change either the whiteboard or the Summary to indicate this is an [X
issue] so that the extension name shows up in those tags to make it easy
to query for specific bugs related to specific extensions.
Do you have thoughts on this? Is there some other process that would
ensure these sorts of problems don't fall through the cracks? Please
follow up to m.d.quality.
Thanks,
Clint