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
- Most nominations for full review are taking less than 10 weeks to review.
- 163 nominations in the queue awaiting review.
- Most updates are being reviewed within 7 weeks.
- 88 updates in the queue awaiting review.
- Most preliminary reviews are being reviewed within 10 weeks.
- 152 preliminary review submissions in the queue awaiting review.
The unlisted queues aren’t mentioned here, but they have very low numbers. We’re in the process of getting more help to reduce queue length and waiting times for all queues. A new admin reviewer started helping us this week and we’re looking for a second one.
If you’re an add-on developer and would like to see add-ons reviewed faster, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.
Firefox 41 Compatibility
The compatibility blog post has been up for a while. The compatibility bump was run on Monday, which is way too late, and I apologize for that. I just lost track of it. Fortunately it was a fairly small validation with very few developers affected.
Firefox 42 Compatibility
Expect the blog post to come up soon. Again, this is something I expected to have done sooner, but it’s coming.
As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition (formerly known as Aurora) to make sure that they continue to work correctly. End users can install the Add-on Compatibility Reporter to identify and report any add-ons that aren’t working anymore.
The wiki page on Extension Signing has information about the timeline, as well as responses to some frequently asked questions. The new add-on installation UI and signature warnings are now enabled in release versions of Firefox.
We recently announced an extension to the signing deadline. The current plan is to turn on enforcement by default in Firefox 43.
Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running content code in a different process than browser code. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.
If you read Kev’s post on the future of add-on development, you should know there are big changes coming. We’re investing heavily on the new WebExtensions API, so we strongly recommend that you start looking into it for your add-ons. If you have requests for new APIs, please suggest them in the uservoice forum.