canmove, Confirmed users
1,448
edits
Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation: Difference between revisions
Jump to navigation
Jump to search
Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation (view source)
Revision as of 20:11, 25 November 2011
, 25 November 2011→Taking action
| Line 14: | Line 14: | ||
When reproduced, the compatibility bug will be qualified to determine the action to take: | When reproduced, the compatibility bug will be qualified to determine the action to take: | ||
* Minor bug: the add-on's main functions work acceptably. | * Minor bug: the add-on's main functions work acceptably. | ||
* 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. | ** The add-on developer will be contacted. | ||
* Critical bug: the compatibility bug breaks Firefox in some way. The add-on developer will be contacted | * Major bug: the add-on is significantly broken. | ||
* Crashes | ** 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. | |||
** 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 == | == Reporting == | ||
The Add-ons Team will produce a weekly report on add-on incompatibility that will be presented in the Product Planning Meeting. | The Add-ons Team will produce a weekly report on add-on incompatibility that will be presented in the Product Planning Meeting. | ||