The archive · Work & Ways of Doing · Technical decision · 2011–2012
Mozilla 2011: Firefox ships every six weeks instead of yearly
Mozilla replaced Firefox's infrequent releases with a six-week rapid release train so features reach users immediately — a cadence the industry adopted.
Mozilla
What it had to solve
Before 2011, Firefox sometimes held new capabilities ready for nearly a year before releasing them. Mozilla's chair Mitchell Baker argued a browser that is the delivery vehicle for the Internet cannot ship like traditional desktop software.
How it works
Before 2011, Firefox shipped like traditional desktop software: new capabilities could sit ready for nearly a year before users got them, and web developers had to wait that year to improve their applications. Mozilla's chair, Mitchell Baker, argued the browser is the delivery vehicle for the Internet, and a product that moves at the speed of desktop software cannot enable an Internet that moves in real time.
So Mozilla adopted a rapid release process in 2011, organizing development around a train model with a release every six weeks. Firefox 5 shipped in June 2011 and Firefox 6 followed in August on the new schedule. The change was controversial: enterprises found six-week change disconcerting, and add-on compatibility became a recurring complaint.
Baker defended the trade in a public retrospective: before rapid release, Mozilla would sometimes have new capabilities ready for nearly a year before delivering them; the six-week train ensured capabilities arrived when they were ready. Mozilla acknowledged the enterprise problem and began exploring long-term support versions for organizations that could not absorb six-week updates.
Why it lands
- It reframed release cadence as a product decision, not an engineering detail: the browser had to move at the speed of the web it delivers.
- The train model made delivery continuous, so a finished feature shipped in weeks instead of waiting for a monolithic annual release.
- It treated the pain openly — Baker published the rationale and the trade-offs, which is what made the process change credible.
- It kept the browser relevant against faster-moving competition by making delivery a constant, not an event.
What it did
Firefox went from roughly yearly releases to a reliable six-week rhythm, and rapid release trains became the industry norm for browsers and software companies; Mozilla later added an extended support release for enterprises that could not absorb six-week updates.
What you can take
When your product is the delivery vehicle for a moving ecosystem, release cadence is a strategic choice: shortening it to match the ecosystem's speed multiplies the value of every finished feature.
Since then
Rapid release became the standard for browsers and spread through the software industry; Mozilla later added an Extended Support Release (ESR) channel for enterprises, and the train model remains the backbone of Firefox's delivery today.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card