When Firefox 3.6 beta 1 came out, I let you know that you should start working on your add-on compatibility for 3.6. Did you listen? No? Well, then you’re going to start hearing from your users, because Firefox 3.6 is now officially out. Within a few days most of the world will be up to date, and your add-ons should be up to date, too.
The add-on review queues are normally very busy during update times, so you should follow these guidelines to make sure your add-on stays up to date and doesn’t have to wait too long for a review:
- Visit Firefox 3.6 for developers and read all about the changes that have been introduced in Firefox 3.6. Some additional information for theme authors is available in this forum topic.
- Test your add-on with the final release of 3.6 and see if there are any compatibility problems. Most add-ons should be fine.
- If the current version of your add-on doesn’t show any compatibility issues, you don’t need to upload a new version. Visit the Developer Hub: https://addons.mozilla.org/en-US/developers/ and change the “max version” value in the latest version of your add-on (it’s in the Versions and Files section). That’s all it takes. Make sure to set your max version to 3.6.*.
- If you need to update your add-on for 3.6, submit your update as soon as possible. There will be an update rush happening soon, and it will probably take a while for the AMO editor team to catch up.
Also, if you have binary components, some important changes have been made to the C API which might affect your add-ons. Make sure you build your add-on against the newest SDK, which is version 1.9.2. The new SDK should be available in the Gecko SDK page.
If you have any questions or comments, don’t hesitate to post here, or at the new AMO forum.