Mozilla to Say Ta-Ta to Foxy Part Deux

November 11th, 2008 by Justin Ryan

Your rating: None

Mozilla's Firefox browser is unquestionably one of the most popular web browsers on the market — topping 20% at times while the browser-to-beat continues to slide — and certainly so among Open Source users. The release of Firefox 3 in June was a major milestone for Mozilla, but still, nearly six months later, there are those who have eschewed the new for the comfortable, homey, well-worn-in welcomeness of Firefox 2. That will be changing soon, though, as funeral arrangements for the second-era Fox are in full-tilt at Mozilla HQ, and the service is fast approaching.

Every Open Source project has its own unique way of replacing the old with the new. Larger projects often maintain parallel releases in active development, while many small projects move from one version to another without maintaining legacy support. Some projects support their legacies for a definite period — Ubuntu is a prime example, supporting each standard release for 18 months, and providing extended support for designated Long Term Support releases — while others utilize a more relaxed approach, dropping archaic versions as the time seems right. Mozilla falls in the former camp, supporting the old version of Firefox for six months after the release of a new one.

The six months alloted to Firefox 2 are rapidly coming to a close, and if all things go as planned, will culminate somewhere near the middle of next month with the release of Version 2.0.0.19. At that point, users will no longer receive security and stability updates for the existing versions, nor will there be any further releases or new features for the 2.0 series. According to Mozilla, two-thirds of its userbase is already using Firefox 3, and despite much dissatisfaction with this and that — as well as more than a few deal-breaking bugs — no doubt much of the remainder will migrate when support ends. Still, there will surely be some who will cling to their familiar friend, and risk exploits and vulnerabilities rather than make the switch, while a small group, if they haven't done so already, will likely opt to change browsers entirely.

It won't, however, be Firefox 2 alone that ends development in December — with the retirement of the 2.0 codebase, Mozilla is also ending further development of Gecko 1.8, the layout engine utilized in the 2.0 series of both Firefox and Thunderbird, as well as the current releases of both SeaMonkey and Camino. Asked what impact the end of 1.8 development would have on these other projects, Mozilla's Mike Beltzner responded "The end of support for Firefox 2.0 doesn't mean that [developers] won't be able to work on the Gecko code. It just means that our focus won't be on actively maintaining that [1.8] branch [of Gecko]."

For now, the only outward indication at Mozilla that anything is happening at all is a brief note on the "all older" page: "Firefox 2.0.0.x will be maintained with security and stability updates until mid-December, 2008. All users are strongly encouraged to upgrade to Firefox 3."
__________________________
Justin Ryan is the News Editor for Linux Journal.
Look for him in the #linuxjournal IRC channel.


Special Magazine Offer -- Free Gift with Subscription
Receive a free digital copy of Linux Journal's System Administration Special Edition as well as instant online access to current and past issues. CLICK HERE for offer

Linux Journal: delivering readers the advice and inspiration they need to get the most out of their Linux systems since 1994.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
BillK's picture

Firefox 3 needs Win XP minimum

On November 13th, 2008 BillK (not verified) says:

Many users cannot run Firefox 3 because it needs at least Win XP. Users of earlier OS versions have to stick with Firefox 2 or change to a different browser. If Opera can support Win 98, why can't Mozilla?

Mozilla should be hoping that the third of users that are still on Firefox 2 don't all switch to Opera instead.
Not by choice. Mozilla are forcing them to switch.

Terrell Prude' Jr.'s picture

Problems with Firefox 3 and LTSP/K12LTSP deployments

On November 11th, 2008 Terrell Prude' Jr. (not verified) says:

Lots of K12LTSP sysadmins are keeping their servers on Firefox 2. There are a number of reasons. Some of them relate to FF3 breaking Adobe Flash (or is it the reverse?) on LTSP thin clients. Other reasons relate to excessive memory usage of Firefox 3 in an LTSP environment (FF2 is much, much better about that). It doesn't look to those of us in this situation that the Mozilla team took that type of scenario into account with FF3.

Yeah, I know, security updates and all, and you'd be right. And yes, Adobe Flash SUCKS. I hate it and do not use it. However, if you want to sell GNU/Linux in American schools, you've gotta be able to do Adobe Flash, unfortunately.

Konqueror is an excellent alternative in this scenario. It makes much better use of shared memory, supports Netscape/Mozilla/Firefox plugins (including the accursed Adobe Flash), is FOSS, and comes with virtually all distros.

--TP

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

From the Magazine

December 2009, #188

If last month's Infrastrucuture issue was too "big" for you then try on this month's Embedded issue. Find out how to use Player for programming mobile robots, build a humidity controller for your root cellar, find out how to reduce the boot time of your embedded system, and if you're new to embedded systems find out the basics that go into one. You can also read about the Beagle Board, the Mesh Potato and a spate of other interestingly named items. And along with our regular columns don't miss our new monthly column: Economy Size Geek.


Read this issue