Mozilla Firefox 4 Release Candidate for Windows, Mac and Linux Now Available
Mozilla Firefox 4 for Windows, Mac and Linux has exited the beta cycle and is now available as a release candidate in more than 70 languages. The millions of users testing Firefox 4 will be automatically updated …
Context & Ripple Effects
The twelfth and final Firefox 4 beta shipped just under two weeks ago, closing out a beta cycle that began in earnest when Mozilla put an early build into 23 languages back in July 2010. The release candidate is the payoff stage of that arc: localization has jumped from 23 languages to more than 70, which is what a code freeze looks like in practice.
The milestone also lands late against Mozilla's own schedule — an executive said in January that Firefox 4 would arrive in February, so the RC in March confirms the slip even as it signals the endgame. Separately, the desktop track now runs parallel to the Android and Maemo beta Mozilla opened last October, making this the first Firefox cycle with a genuine mobile sibling.
First-order effects
- Millions of Firefox 4 beta testers are automatically moved onto the release candidate, per Mozilla, so the RC population effectively becomes the final-launch staging group overnight.
- Localizers and extension developers shift from feature work to validation: with more than 70 languages in the RC, remaining changes are limited to ship-blocking bugs.
Second-order effects
- A frozen desktop codebase frees Mozilla's engineering attention for the Android and Maemo builds, putting pressure on the mobile browser field where Firefox is the newcomer.
- Rivals on faster release cadences get a clear window: every week between this RC and the final launch is time for competing browsers to ship updates against an unchanging Firefox target.
Third-order effects
- If the pattern holds, browser version numbers stop marking distinct products and start marking checkpoints on a continuously updated train — with release candidates functioning as broad-scale dress rehearsals rather than discrete events.
- The scale of the automatic-update path (millions of testers promoted in place) makes the installed base itself part of the QA process, a structural shift in how major software ships.
The trend: Browser development is converging on continuous, auto-updated release trains in which beta populations double as distribution infrastructure, compressing the gap between 'testing' and 'shipping'.