kripkenstein wrote:
There is a big tradeoff here, with downsides both ways. You correctly point out that some people are having problems with the new fast release schedule. That's a fact, and we are doing all we can, but the problems are hard (addons, enterprise users, etc.).

On the other hand, the alternative is to continue with a slow release schedule, which we feel has bigger problems and would annoy more users. For example, FF8 will have much better memory usage than Firefox 4. Releasing new versions quickly lets users get that benefit quicker - fewer users will have memory problems because we ship the fixes faster. As another example, when IE9 and FF4 came out, at roughly the same time, they had comparable performance on some canvas benchmarks (in which they outperformed all other browsers due to their being the only browsers to use Direct2D). Meanwhile Firefox has released twice (counting FF6 on next Tuesday), and as a consequence, Firefox users have better performance than IE users, simply because IE users are still on IE9 while Firefox users can run FF5 and FF6 which include a lot more performance improvements that were committed after FF4.

Another major issue is new web standards. For standards to evolve quickly, browsers need to ship new versions with new implementations of those standards. Firefox and Chrome are now leading that, by releasing every 6 weeks. As one example, both support the new (safe) version of web sockets. That pushes the web forward, letting developers use it quicker, and eventually let all of us benefit from those new features. Chrome began this push, and I think Google was right to do it, and Firefox is joining that.

Is the new release schedule perfect? Of course not. It has problems for both browsers doing it, Chrome and Firefox. Both are probably not seen very favorably among enterprise users. And Firefox has some additional challenges, what with transitioning a previous release schedule to this one. But still, both Chrome and Firefox feel it is worthwhile. So again, I realize that there are problems. But overall I think the fast release schedule of Chrome and Firefox is a good thing.

The problem is that Chrome and Firefox 6-week updates can and do change functionality and break internal APIs. Regardless of whether those browsers raise the major version number, addons can break.

Chrome deals with this by having a limited addon API that does remain stable. This limits what addons you can write for Chrome, but it does make 80% of addons possible and with less upgrade hassle.

Firefox is moving to allow that approach with the jetpack SDK. However addons that don't use that SDK are relying on internal Firefox APIs, and the power and flexibility that that gives does mean they are at risk for breaking. Note that Mozilla's addons website will automatically check the code of addons hosted on it for actual API incompatibilities, and auto-mark as compatible addons that are not at risk. So a lot of addons 'just work' because of that. But still, some addons do rely on changing APIs, and some addons are not hosted on addons.mozilla.org, so the authors need to manually update them.

Code:

Source:http://slashdot.org/story/11/08/14/1534259/Mozilla-Firefox-6-Released-Ahead-of-Schedule