Add-ons Review Update – Week of 2011/03/29

Jorge Villalobos

2

I post these updates every 2 weeks to inform add-on developers about the status of the review queues and any other important stuff going on in the add-ons world.

Summary

  • Nominations for full review at the moment are being processed slower than usual. The new review system required hundreds of add-on developers to renominate their add-ons, which has placed a large workload on the editor team. Nominations are currently taking several weeks (~4) to review.
  • Most updates are being reviewed within 5 days. An avalanche of updates were submitted following the final Firefox 4 release, so we have been spending extra time keeping updates in line.
  • Most preliminary reviews are being reviewed within 10 days.

The Review Queues

  • These stats are taken from the last queue report.
  • 64 new nominations that week. 224 nominations in the queue awaiting review.
  • 238 new updates that week. 114 updates in the queue awaiting review.
  • 187 new preliminary review submissions that week. 209 in the queue awaiting review.
  • 1252 reviews performed by AMO Editors in March.

Firefox 4 Compatibility

Firefox 4 is out! If your add-on is already compatible, you should update your maxVersion to 4.0.* to cover all future 4.0 releases. Most of the necessary documentation to upgrade your add-on for Firefox 4 is readily available:

The Compatibility Dashboard shows how we stand in the compatibility front. Of the most popular add-ons (95% of usage), 85% are already compatible with Firefox 4. This number has been growing a percentage point every couple of days since the release, so here’s to 90%! :)

Notes for Developers

  • Mozilla has been focused on performance for quite some time now, and add-ons are no exception. We’re reaching out to authors about this and we recommend all authors to read and implement the recommendations we have on our Add-on Performance Best Practices documentation. AMO will integrate performance metrics for all listed add-ons  very soon, and you don’t want to be left behind!
  • If your add-on listing has been disabled, it could be related to the mass sandbox cleanup we performed recently. You can still get it enabled again if you contact us. There are instructions on your add-on page.
  • The AMO Editor Guide. This is a comprehensive guide to the work performed by AMO Editors. If you want to have a clear idea of how we test add-ons, or you’re interested in joining us, this is a good place to begin.
  • Useful Information for Add-on Authors. How to improve review times for your add-on, information about the review process, etc.

Jorge Villalobos

Add-ons Developer Relations Lead, Mozilla

2 responses

  1. Tony Mechelynck wrote on ::

    Firefox 4 is out! If your add-on is already compatible, you should update your maxVersion to 4.0.* to cover all future 4.0 releases.

    Also, nightlies of Firefox 4.2a1pre and SeaMonkey 2.2a1pre are now being produced. If an extension (available at addons.mozilla.org) is already compatible with these nightlies, can its author mention the fact in the maxVersion, or will testers have to override compatibility if they want to use extensions with these new test builds?

    1. Jorge Villalobos wrote on ::

      It’s already possible to do this on AMO, yes. Both Firefox and SeaMonkey nightlies are supported.