Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation: Difference between revisions
Jump to navigation
Jump to search
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 | * 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. | ||
Revision as of 20:09, 25 November 2011
Default to Compatible - Detection and Mitigation
Gathering data
The Add-ons Team will be informed about compatibility problems with pre-release versions of Firefox through 3 channels:
- Reports submitted from the Add-on Compatibility Reporter.
- Bugs filed in the Extension Compatibility component in Bugzilla.
- SUMO reports.
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.
- 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 this link.
- SUMO: ?
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.
When reproduced, the compatibility bug will be qualified to determine the action to take:
- Minor bug: the add-on's main functions work acceptably. No action taken.
- Major bug: the add-on is significantly broken. The add-on developer will be contacted. If the breakage continues to happen on Beta, the add-on version will be added to the blacklist.
- Critical bug: the compatibility bug breaks Firefox in some way. The add-on developer will be contacted and the add-on version will be added to the blacklist immediately. The developer will be encouraged to use the no-dtc flag in install.rdf.
- Crashes: same as critical bugs, but the regular crash procedure should also be followed, with the possibility of blocklisting.
Reporting
The Add-ons Team will produce a weekly report on add-on incompatibility that will be presented in the Product Planning Meeting.