- These 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 as well.
- Most nominations are being reviewed within 2 weeks. Our goal is have them all under 2 weeks by April.
- Almost every update is being reviewed within 4 days. We want to reduce this even more in the future, but nominations are the current priority.
The Review Queues
- The stats are taken from the latest queue report from last Friday.
- 61 new nominations that week. 126 nominations in the queue awaiting review.
- 66 new updates that week. 67 updates in the queue awaiting review.
- 1296 reviews performed by AMO Editors so far in March. There were 20 editors performing reviews last week.
See the Add-on Review Process and You for information on how to check your current add-on status.
Notes for Developers
Everyone 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. This is not a decision we’re taking lightly, and we need to find a way to provide a safe experience for all of our users.
- 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.
- I posted a general Add-on Policy Update today, describing all recent (and some not-so-recent) policy decisions. Everybody should have a look.
- I’m currently working on porting the XUL School Tutorial for Extension Developers to MDC. I expect it to be finished tomorrow, and I’ll be making an announcement on this blog about it.
Add-ons Developer Relations Lead, Mozilla