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.
- 233 nominations in the queue awaiting review.
- Most updates are being reviewed within 7 weeks.
- 101 updates in the queue awaiting review.
- Most preliminary reviews are being reviewed within 10 weeks.
- 268 preliminary review submissions in the queue awaiting review.
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 39 Compatibility
The Firefox 39 compatibility blog post is up. The automatic compatibility validation will be run probably later this week.
Firefox 40 Compatibility
The Firefox 40 compatibility blog post is also coming up.
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.
We announced that we will require extensions to be signed in order for them to continue to work in release and beta versions of Firefox.
Yesterday I posted this update of where we are with signing on AMO. In a nutshell, all AMO extensions for Firefox that passed review have been signed, and all new versions will be signed once they pass review. We have enabled Unlisted extension submission, but it’s currently under testing, so expect some bugs. The major issues will be resolved in the coming week and we’ll make an announcement on this blog to indicate we’re ready for your submissions.
The wiki page on Extension Signing has information about its timeline, as well as responses to some frequently asked questions.
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.
We will be talking more about these changes in this blog in the future. For now we recommend you start looking at the available documentation.