Mozilla dumps Firefox 3.7 from schedule, changes dev process
Plans to quicken development pace by adding some features via security updates — Computerworld - Mozilla has made major changes to how it develops Firefox, and plans to drop Firefox 3.7 from its schedule and instead roll …
Context & Ripple Effects
The move is the third act in a familiar Mozilla cycle: performance problems forced a roadmap change around Firefox 3 back in 2007, a slipped beta stretched out the 3.1 cycle through early 2009, and late last month Mozilla conceded that 3.6 had missed its predicted December final-release date while giving 4.0 more time to bake. Each slip has ended in a process overhaul rather than just a new date.
This time the fix is structural rather than calendrical: instead of inserting another interim stopgap between 3.6 and the long-gestating 4.0 — the role 3.7 was drawn up for — Mozilla will fold some features into what are nominally security updates, effectively using its maintenance channel as a feature pipeline.
First-order effects
- Firefox 3.6 becomes the last stop before 4.0 on the numbered track: features once earmarked for 3.7 reach users through incremental updates instead of a discrete mid-cycle upgrade.
- Mozilla's release engineers now own two jobs at once — shipping critical fixes like the November stability-and-security patch stream and vetting new features riding along in those same updates.
Second-order effects
- Enterprises and add-on developers that certify against specific Firefox versions face a blurrier target: a 'security update' can no longer be assumed feature-free, raising regression-testing work with each patch.
- Rival browser vendors are put under implicit pressure to match the faster feature-delivery pace, since Mozilla is shortening the gap between user-visible improvements without waiting for major launches.
Third-order effects
- If the pattern holds, Firefox version numbers lose their meaning as feature markers and release engineering — not feature scope — becomes the binding constraint on the browser's cadence, echoing how the 2007 crisis forced a roadmap rewrite.
- The change points toward a continuous-release model in which the distinction between maintenance channel and feature channel erodes industry-wide, a shift whose stability costs remain an open question given Mozilla's history of slips.
The trend: Browser development is moving from milestone-numbered majors toward rolling delivery, with security-update channels doubling as feature pipelines.