- These bi-weekly posts explain the current state of add-on reviews and other information relevant to add-on developers. There’s a lengthy overview of the Add-on Review Process posted in this blog that should be read as a general guide for the process.
- Most nominations are being reviewed within 2 weeks. Our goal is have them all under 2 weeks by May.
- Almost every update is being reviewed within 4 days. We want to reduce this more in the future, but nominations are the current priority.
- The frequency of these reports has been reduced to bi-weekly (starting with this one) in order to reduce the noise/content ratio.
The Review Queues
- The stats are taken from the latest queue report from last Friday. Note: on Friday we discovered about 100 add-on updates with incorrect status due to an AMO bug. Their status was fixed and they have all been reviewed or received editor feedback by now.
- 62 new nominations that week. 105 nominations in the queue awaiting review.
- 82 updates that week. 82 updates in the queue awaiting review.
- 262 reviews performed by AMO Editors this month. There were 18 editors performing reviews last week.
See the Add-on Review Process and You for information on how to check your add-on status.
Notes for Developers
- Useful Information for Add-on Authors. How to improve review times for your add-on, information about the review process, etc.
- Bugzilla information for editors. How to file AMO bugs, how to flag bugs relevant for editors, and information on current and future AMO version releases. Let me know if you want to help fixing AMO bugs.
- Gavin Sharp recently blogged about upcoming changes to the tab context menu.
- If you have an add-on that uses the XPCOM Plugin API and have been experiencing problems migrating to 3.6, please read these discussions at the AMO Forum.
- You should read Justin Scott’s post on the proposed changes for the AMO sandbox model. This proposal will substantially change the way we see and deal with unreviewed add-ons, and will have a significant impact on all add-on developers. The proposal has since been updated and the incubation period has been extended to 90 days.
Add-ons Developer Relations Lead, Mozilla