The Mozilla 1.0 Media Circus
Friday June 7th, 2002
The release of Mozilla 1.0 was reported by most tech news sites including BetaNews, CNET News.com, evolt.org, eWEEK, ExtremeTech, Geek.com Geek News, IDG.net, internetnews.com, Internet Week, LinuxMAX, Linux Today, MacSlash, MozillaNews, NeoWin.net, Slashdot, The Register, vnunet.com, WinInfo and ZDNet News. More mainstream news sites are also taking notice. BBC News has an article and smh.com.au (the online edition of The Sydney Morning Herald) reported on Mozilla a few days ago.
Taking a slightly different approach, PC Magazine marks the release with an interview with Mitchell Baker while ITBusiness.ca talks with Mike Shaver. Meanwhile, kuro5hin has an opinion piece about the release.
Mozilla 1.0 scored 7 out of 10 in CNET's review, which describes Mozilla as "the best free alternative to Microsoft IE." Meanwhile, eWEEK's analysis notes that "Mozilla makes it possible for any developer or company to customize the browser to be whatever they need it to be." NewsForge also discusses Mozilla's customizability. In addition, there's a Slashdot piece on the Mozilla 1.0 reviews.
On a related note, CNET has a video that recaps the browser wars and asks if Netscape 7.0 will revive the battle.
Thanks to everyone who sent us links to news and reviews.
#14 Re: Is the profile stable?
Sunday June 9th, 2002 11:00 AM
You are replying to this message
"... are we done with the remove-all-files-from-any-previous-version routine after 1.0?"
If you are upgrading from one 1.0.x branch build to another then I expect you would not need to scrap your profile. Any changes on that branch should be restricted to bug fixes and improvements that preserve backward compatibility with earlier branch builds. The trunk, on the other hand, is a different matter. The trunk *might* at some point accept a major change to the code that will obsolete your profile. This might be necessary to accommodate new features or new implementation of existing ones.
Those seeking a stable profile should restrict themselves to using 1.0.x branch builds. Hopefully before the 2.0.x branch is cut (-: 2010? :-), mozilla will have migration tools that will make the need changes to upgrade a 1.0.x profile to whatever a 2.0.x profile will look like.