Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation: Difference between revisions

No edit summary
Line 6: Line 6:
* SUMO reports.
* SUMO reports.
== Triaging data ==
== Triaging data ==
* Add-on Compatibility Reporter: AMO will have a dashboard that will show compatibility reports sorted by report count and usage stats. The dashboard should also be filtered by Firefox version. All reported add-ons with more than 50 (?) negative reports should be tested to try to reproduce.
* Add-on Compatibility Reporter: AMO will have a dashboard that will show compatibility reports sorted by report count and usage stats. The dashboard should also be filtered by Firefox version.
* Bugzilla: all compatibility breakage reports that correspond to pre-release Firefox versions should have [dtc] set in the whiteboard. Any communications suggesting to file bugs should use [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Extension%20Compatibility&status_whiteboard=%5Bdtc%5D this link].
* Bugzilla: all compatibility breakage reports that correspond to pre-release Firefox versions should have [dtc] set in the whiteboard. Any communications suggesting to file bugs should use [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Extension%20Compatibility&status_whiteboard=%5Bdtc%5D this link].
* SUMO: ?
* SUMO: ?
== Taking action ==
== Taking action ==
Add-ons that are repeatedly reported will be tested by the Add-ons Team to verify the breakage. If the problem is hard to reproduce or the workload becomes significant, the QA Team will be asked to help.
Add-ons that are repeatedly reported will be tested by the Add-ons Team to verify the breakage. If the problem is hard to reproduce or the workload becomes significant, the QA Team will be asked to help.
canmove, Confirmed users
1,448

edits