Categories: developers

Add-ons Review Update – Week of 2010/03/23


  • 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. At this moment, only 10% of all nominations (14 out of 140) have waited longer than 2 weeks.
  • 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.
  • 86 new nominations that week. 167 nominations in the queue awaiting review.
  • 104 new updates that week. 105 updates in the queue awaiting review.
  • 955 reviews performed by AMO Editors so far in March. There were 18 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. Version 5.8 of AMO will be pushed live tonight. See the list of 5.8 bugs if you’re interested.
  • Support for the signed.applets.codebase_principal_support preference and the enablePrivilege function will be dropped soon. Add-on authors that rely on this feature will need to find alternatives for it immediately, and editors will begin rejecting add-ons that use any of these features very soon.
  • Private Browsing Mode support will soon become a requirement for add-ons that handle browsing data. We will probably start reviewing for PBM support on April 2nd.
  • I’m currently working on porting the XUL School Tutorial for Extension Developers to MDC.
  • I wrote a post with some ideas for improving add-on packaging that I think would help lower the barrier of entry for new developers. It’s nothing official, but I would like to get as much feedback as possible.

Jorge Villalobos

Add-ons Developer Relations Lead, Mozilla