I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.
The Review Queues
- Nominations for full review at the moment are being processed slower than usual. Most nominations are taking about 5 weeks to review.
- Most updates are being reviewed within 10 days.
- Most preliminary reviews are being reviewed within 4 weeks.
These stats are taken from the last queue report:
- 67 new nominations that week. 243 nominations in the queue awaiting review.
- 111 new updates that week. 126 updates in the queue awaiting review.
- 44 new preliminary review submissions that week. 267 preliminary submissions in the queue awaiting review.
If you compare these numbers to the last report, you’ll see we’re improving on most fronts. We continue to ramp up our efforts, and we’re in the process of introducing new editors from the Jetpack team, who should be able to help reviewing SDK-based add-ons.
If you’re interested in joining the AMO Editors team and help us review add-ons, please read the page on How to Apply.
The Firefox 8 compatibility post is here.
You should note that there are a couple of possible reversals coming into Firefox 8 that affect add-on developers, mostly in good ways:
- Bring back ISO8601DateUtils.jsm. Since the Date object isn’t exactly equivalent to this module and some significant add-on breakage was expected from its removal, it will be brought back for the time being. You should still change your add-ons so that it isn’t used anymore, but it’ll be at least one more release before it is completely removed.
- Back out bug 455694 (tab drag/detach animations). There is no final decision on this yet. The backout patch has been checked in for testing and you should track this bug if it affects your add-on.
- 3rd party add-on check doesn’t disable add-ons that were installed into the profile or application folder. The third party add-on check is being extended to include add-ons installed directly in the application folder or in the profile. This doesn’t affect any add-ons installed through the regular add-on installation process, or if they are installed manually from a local file. This should only affect add-ons that are automatically installed from an external package and copied into these other locations. It can affect add-on developers who have automatic installation processes to test their new code. You should read this comment for information on how to bypass this check and avoid the dialog at startup.
The Firefox 9 compatibility post is here. The compatibility bump to Firefox 9 was run last week, so any add-ons with compatibility under 9.* should be tested and manually upgraded in the Developer Hub, if possible.
You can run the standalone compatibility tool if you want to test your add-on yourself or if it isn’t hosted on AMO.
We strongly recommend that you aim to make your add-on compatible with the Firefox version in the Aurora channel, Firefox 9 at this moment. Making your add-on compatible with Aurora qualifies it for our automatic compatibility upgrades, saving you lots of time. If you need more information about this, don’t hesitate to ask.