Mozilla Add-ons Community Blog
Categories: compatibility developers documentation

Add-ons Update – Week of 2011/11/17

5 responses

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 6 weeks to review.
  • Most updates are being reviewed within 2 weeks.
  • Most preliminary reviews are being reviewed within 3 weeks.

These stats are taken from the last queue report:

  • 82 new nominations that week. 247 nominations in the queue awaiting review.
  • 116 new updates that week. 149 updates in the queue awaiting review.
  • 66 new preliminary review submissions that week. 104 preliminary submissions in the queue awaiting review.

If you’re interested in joining the AMO Editors team and help us review add-ons, please read the page on How to Apply.

Firefox 8

There’s a bug that affects themes in Firefox 8, in Mac OS X Lion. Please read this blog post if you’re a theme developer.

Firefox 9

The Firefox 9 compatibility post is here. The compatibility bump to Firefox 9 was run weeks ago, 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. 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.

Firefox 10

Compatibility update coming soon!

5 comments on “Add-ons Update – Week of 2011/11/17”

  1. Sasha van den Heetkamp wrote on

    Hi Jorge, I bumped one add-on to 9.* that I added today. Can I bump it to 10.* as well? Since I’m fairly sure nothing will break it in 10. Or will it be bumped automatically to 10.* after manually bumping it to 9.* ?

    1. Jorge Villalobos wrote on

      If your add-on has a maxVersion of 9.*, it will qualify for the 10.* bump, which is currently planned for next week. So, your add-on should be bumped if everything goes well. You’re of course welcome to test yourself and bump it yourself if you want to.

  2. Tony Mechelynck wrote on

    Hi Jorge, I’m running bleeding-edge nightly builds as my day-to-day browser and mailer (live-testing them, if you will), with only minor problems. I have quite a number of extensions installed (forty or so enabled at last count) and I wonder at the discrepancy between how many actually work but how few have the appropriate maxVersion. I suppose there’s nothing to do about it (other than set extensions.checkCompatibility.nightly to false and report compatibility through the ACR)? Maybe try to convince extension authors but almost all of them seem to have cold feet about supporting a1 nightlies?

    1. Jorge Villalobos wrote on

      Hey Tony. The Default to Compatible feature is exactly what you need and will get very soon. Pre-release versions of Firefox will override compatibility by default, and we will only blacklist compatibility information for those add-ons that are detected as incompatible.

      Telling add-on developers to support nightly is asking too much IMO. Most barely have the time to test on beta and keep up with releases, which is why we came up with the compatibility bumps and now are moving to default to compatible.

      1. Tony Mechelynck wrote on

        Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111123 Firefox/11.0a1 SeaMonkey/2.8a1 ID:20111123003001

        Well, I’m going to watch for this, and if needed I’ll nag my fellow SeaMonkey community members so they don’t forget to make sure it works here too. And I’ll go on using the ACR to report “incompatible” addons that work with me, so they get good karma at AMO.