Why Firefox Rapid Release Schedule Is a Bad Idea
Mozilla has committed to a more aggressive release schedule for the Firefox Web browser. There were nearly three years between the launch of Firefox 3 and Firefox 4, but Firefox 5 is expected to be introduced in a matter of months at the end of June.
Context & Ripple Effects
The criticism lands at the end of a long arc of schedule churn: Mozilla pushed back the Firefox 3.6 and 4.0 deadlines in late 2009, then delayed Firefox 4 into 2011, and finally shipped it on March 22 after a twelve-beta cycle. In February, Mozilla's roadmap called for versions 4 through 7 all before the end of 2011 — the rapid-release commitment PC World is now pushing back on.
The shift traces back to January 2010, when Mozilla dropped Firefox 3.7 from the schedule and changed its development process. What was then a one-off restructuring has hardened into a standing cadence, and the gap between the nearly three years separating Firefox 3 and Firefox 4 and a Firefox 5 due by end of June is what makes analysts call the new pace a mistake.
First-order effects
- Firefox users face a version-number treadmill: with Firefox 5 due within months of March's Firefox 4 launch, enterprises and add-on developers who just finished qualifying Firefox 4 must re-test against each new major version.
Second-order effects
- Add-on and extension maintainers bear the brunt — a cadence this fast forces compatibility updates several times a year, raising maintenance costs for the ecosystem that differentiates Firefox from rivals like Chrome, which already runs a rapid cycle.
Third-order effects
- If the roadmap holds through versions 4–7 in 2011, browser version numbers stop signaling feature milestones and become mere timestamps — pressuring every browser maker toward continuous release trains and forcing IT departments to treat browsers as continuously updated infrastructure rather than discrete deployments.
The trend: Browser development is converging on Chrome-style rapid release trains, trading long, stable major versions for a continuous cadence that shifts the testing burden onto enterprises and extension developers.