As Mozilla is wrapping up the development process for the Beta 2 stage of Firefox 3.0 now due on December 21st, it is clear that the next version of the open source browser will hit in early 2008. And taking into consideration the proximity of the final version of Firefox 3.0, just a few betas away, questions come to mind, focused on the future compatibility of the existing extensions. An advanced level of customization is a strong incentive for the adoption of Firefox, and one of the aspects that have become somewhat synonymous with the open source browser. Personalization via add-ons, add-ins and themes is an advantage Firefox has, in comparison with the far more rigid Internet Explorer. This is why it is essential for Mozilla and the environment built around the browser to ensure the continuation of extension support, for the upcoming Firefox 3.0.

"As we get closer to the release of Firefox 3, extension and theme compatibility with the new browser is an important issue. We all want to ensure that when Firefox 3 is launched, users do not find that all of their extensions have been disabled because of incompatibility or insecure updates. Extension authors should be mindful of the following changes that will affect them when updating for Firefox 3. Firefox 3 will use a three-part versioning system, as opposed to the four parts used in Firefox 2. In order to specify compatibility with security and stability releases, authors should use 3.0.* instead of 3.0.0.*. [And ] Extensions now require a secure update channel to function - either by using an updateURL with SSL or by using a new updateKey", revealed Mozilla.

On the Mozilla Developer Center beta, builders will be able to access a resource that will guide them through the process of ensuring that an existing Firefox extension, compatible with the latest iteration of Firefox 2.0 or with a beta build of Gran Paradiso, will also support the final release of Firefox 3.0. At the same time, developers will not be able to jump ahead and use the three-part versioning system just yet, as implementation efforts mush be focused on the exiting testing milestones of Firefox 3.0.