302
edits
Add-ons/QA/Testplan/Add-ons Post Reviews Process: Difference between revisions
Add-ons/QA/Testplan/Add-ons Post Reviews Process (view source)
Revision as of 12:19, 20 June 2017
, 20 June 2017→Overview
ValentinaP (talk | contribs) |
ValentinaP (talk | contribs) |
||
| Line 10: | Line 10: | ||
= Overview = | = Overview = | ||
* | * Add-ons listed on AMO are all pre-reviewed by a team of employees and volunteers. This process creates problems with waiting times, especially for add-ons escalated for special review, leading to developers to choose self-hosting or not develop for Firefox at all. | ||
We aim to a post-review model (for WebExtensions), where they are approved and published - if they pass a series of automatic tests - and manually post-reviewed. | |||
== | |||
* | == Goal == | ||
* Automatically approve WebExtensions without human intervention; human reviews are done after the add-on has been pushed to public, prioritized depending on various factors. | |||
=== Entry Criteria === | === Entry Criteria === | ||