Firefox follows Chrome lead, eyes faster releases
Not copying Chrome, says Mozilla exec, just wants to get features in users' hands faster
Computerworld - Once Firefox 4 is out the door next week, Mozilla will likely shift to a faster development cycle for its browser, one that resembles the way Google rolls out a constant line of updates for Chrome.
But don't ask Mozilla if it's copying its rival.
"No one invented fast," said Johnathan Nightingale, director of Firefox development, when asked whether Mozilla's new faster-paced scheme was a response to Google. "We're developers, we want to get our features out there as quickly as possible."
According to a detailed proposal published earlier this week, Mozilla is considering a multi-channel scheme where new features are added to a series of versions -- nightly, experimental, beta and Firefox -- each of which feeds into the next-most-stable build until a polished edition is released.
The pace should result in a new Firefox every 16 weeks, meaning that Mozilla will ship Firefox 5 and 6, perhaps even Firefox 7, during 2011.
Google uses a similar process to continually feed features to Chrome, relying on a four-channel line of development: nightly, dev, beta and stable. The result? A new version of Chrome every six to eight weeks.
Al Hilwa, an analyst with IDC, praised Mozilla's plan. "It is great to see Mozilla looking hard at streamlining their development to achieve a faster release cycle," said Hilwa. "There are a lot of benefits to smoothing and streamlining the development process to release it from the tyranny of dates."
But Mozilla's clearly reacting to the pressure from Chrome, Hilwa added. "Chrome's development model has been a successful experiment in terms of getting production releases with improvements and new features out quickly and much faster than in the past," Hilwa said. "This is causing waves in the industry, specifically for direct competitors."
The change Firefox users would immediately notice under the faster scheme is that new features will regularly appear in the browser, rather than waiting for months while work on the next edition is completed.
"Each release happens regardless of whether a given feature is ready, and releases are not delayed to wait for a feature to stabilize," said the planning document, which was posted by Firefox developer Rob Sayre. "The goal of the process is to provide regular improvements to users without disrupting longer term work."
"'Switch to tabs' was done in September," said Nightingale, referring to a new feature that will debut in Firefox 4 when it launches next Tuesday. "That killed [the feature's developers], having to wait."
Google announced a speedier development cycle in July 2010, when a Chrome program manager explained that the change meant "if a given feature is not complete, it will simply ride on the next release train when it's ready."
- Workarounds to purge search bar from Firefox's new tab page are available
- Mozilla ships Firefox 31, adds search to new tab page
- Microsoft's IE steps back from the brink of irrelevance
- Firefox falters, falls to record low in overall browser share
- Firefox risks user backlash by adding search box to new tab page
- Google unseats Microsoft as the U.S. browser powerhouse
- Safari, Chrome push to mask URLs
- Chrome on Windows champs at the 64-bit
- Google pulls trigger, cripples some Chrome add-ons
- Microsoft shoots to shorten Internet Explorer's long tail
- The Business Value of Continuous Delivery Download this whitepaper to learn more about the business value of Continuous Delivery and see why it could be a game changer for...
- Ten Factors Shaping the Future of Application Delivery Download this research report conducted by Enterprise Management Associates (EMA) to learn how those that are seeking to accelerate application delivery are leveraging...
- HTTP Status Code Cheat Sheet Look at the Graph, Find the Code and Boom - You're Solving Problems. Identifying and understanding common HTTP status codes can go a...
- Architects lead the next generation of data-driven applications Read this whitepaper to find out how application architects can quickly and confidently deliver long-lasting applications that minimize cost, complexity, and risk while...
- Keep Servers Up and Running and Attackers in the Dark An SSL/TLS handshake requires at least 10 times more processing power on a server than on the client. SSL renegotiation attacks can readily...
- On Demand: Mastering the Art of Mobile Content Management Mobile device usage in the enterprise has skyrocketed, and it continues to escalate. IT must answer to users who demand access to their... All Desktop Apps White Papers | Webcasts