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 9 weeks to review.
- 201 nominations in the queue awaiting review.
- Most updates are being reviewed within 4 weeks.
- 55 updates in the queue awaiting review.
- Most preliminary reviews are being reviewed within 5 weeks.
- 135 preliminary review submissions in the queue awaiting review.
Queue numbers this week are pretty bad, but they were much worse last week. Is this good news? Well, yes, we have a new (part time) admin reviewer on board who should help us with the trickier reviews that most volunteers can’t or won’t touch. Hopefully this will cut down waiting times significantly. We also have some policy changes planned that will cut down review times in the near future.
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 33 Compatibility
The Firefox 33 compatibility blog post has been up for some weeks.
The surprise release of version 33.1 included a couple of not-so-great surprises for add-on developers, specifically for complete themes and add-ons using binary XPCOM. Fortunately they were fairly minor issues and we have received good and timely responses from developers.
Firefox 34 Compatibility
The Firefox 34 compatibility blog post will be up very soon. The automatic AMO validation will be run probably next week.
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.
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 each content tab in a different one. 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 near future. We will also begin contacting developers about add-ons malfunctioning with e10s very soon. For now we recommend you start looking at the available documentation.