canmove, Confirmed users
1,448
edits
Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation: Difference between revisions
Features/Add-ons/Add-ons Default to Compatible/Detection and Mitigation (view source)
Revision as of 20:17, 25 November 2011
, 25 November 2011→Taking action
| Line 16: | Line 16: | ||
* Minor bug: the add-on's main functions work acceptably. | * Minor bug: the add-on's main functions work acceptably. | ||
** The add-on developer will be contacted. | ** The add-on developer will be contacted. | ||
** Bugs are resolved as WONTFIX noting that the developer might fix it in the future. | |||
* Major bug: the add-on is significantly broken. | * Major bug: the add-on is significantly broken. | ||
** The add-on developer will be contacted. | ** 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. | ** If the breakage continues to happen on Beta, the add-on version will be added to the blacklist. | ||
** Bugs are resolved as FIXED when the bug is fixed or the version is blacklisted. | |||
* Critical bug: the compatibility bug breaks Firefox in some way. | * Critical bug: the compatibility bug breaks Firefox in some way. | ||
** The add-on developer will be contacted. | ** The add-on developer will be contacted. | ||
** The add-on version will be added to the blacklist immediately. | ** 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. | ** The developer will be encouraged to use the no-dtc flag in install.rdf. | ||
** Bugs are resolved as FIXED when the version is blacklisted. | |||
* Crashes. | * Crashes. | ||
** Same as critical bugs, but the regular crash procedure should also be followed, with the possibility of blocklisting. | ** Same as critical bugs, but the regular crash procedure should also be followed, with the possibility of blocklisting. | ||