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
In the past 3 weeks, 1277 listed add-ons were reviewed:
- 1192 (93%) were reviewed in fewer than 5 days.
- 68 (5%) were reviewed between 5 and 10 days.
- 17 (1%) were reviewed after more than 10 days.
There are 67 listed add-ons awaiting review.
You can read about the recent improvements in the review queues here.
If you’re an add-on developer and are looking for contribution opportunities, 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 48 Compatibility
The compatibility blog post for Firefox 48 is up. The bulk validation should be run in the coming weeks.
As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition 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 current plan is to remove the signing override preference in Firefox 48. This was pushed back because we don’t have the unbranded builds needed for add-on developers to test on Beta and Release.
If your add-on isn’t compatible with multiprocess Firefox (e10s) yet, please read this guide. Note that in the future Firefox will only support extensions that explicitly state multiprocess compatibility, so make sure you set the right flag:
- WebExtensions are compatible by default and don’t need any flags to be set.
- SDK extensions need to set the multiprocess permission in package.json.
- All other extensions need to set the multiprocessCompatible flag in install.rdf.