The dev team over at mozilla.org have quietly released RC2 to the FTP.
There is no announcement or changelog yet but sharp-eyed hajj_3 posted the location to grab the file on our Back Page News section of the forums.
Firefox 2 will be based on continued development of the Gecko 1.8 branch created for Firefox 1.5. The goal is that Firefox 1.5 and 2 are compatible from a web developer's point of view. The final build of 2.0 is expected to be released Q3 this year.
Download via FTP: Firefox 2.0 RC2 for Windows (English) | Other languages ~ 5.7 MB
Download via FTP: Firefox 2.0 RC2 for Linux x86 (English) | Other languages ~ 9.3 MB
Download via FTP: Firefox 2.0 RC2 for Mac OS (English) | Other languages ~ 17.9 MB
View: Firefox 2.0 Roadmap
Link: Neowin Discussion
There is no announcement or changelog yet but sharp-eyed hajj_3 posted the location to grab the file on our Back Page News section of the forums.
Firefox 2 will be based on continued development of the Gecko 1.8 branch created for Firefox 1.5. The goal is that Firefox 1.5 and 2 are compatible from a web developer's point of view. The final build of 2.0 is expected to be released Q3 this year.
LeeŽ contributed to this report

Also, please PLEASE don't link straight into:
- ftp://ftp.mozilla.org/pub/mozilla.org/fir...eleases/2.0rc2/
since that's a single server. Instead use:
- http://releases.mozilla.org/pub/mozilla.or...eleases/2.0rc2/
which is the mirroring system with load balancing and much more bandwidth.
Updated the links..
There's been at least one close call, but not yet.
But why will it take this happening to act as a deterrent to posting 'OMG Firefox is released!!!!" as news, when it's not really out? The downloads page http://www.mozilla.org/projects/bonecho/all-rc.html isn't updated (and states a probably release date and time), the RC 2 release notes aren't posed, other Firefox 2 RC 2 documentation on the website isn't available either and the update system hasn't been turned on.
What I don't understand is what news site like neowin et al get from preempting or second guessing mozilla. It's not like they're going to put binaries up and then not announce the release or something. There's a bunch of steps that have to be complete to make a release final, and getting the binaries onto the ftp mirrors is just one of those steps.
One day builds in the ../release/ dir will get pulled for some reason, and then there'll just be confusion for all the news sites who announced the release and all those who downloaded the build. I don't understand why waiting a bit longer for the official announcement on the downloads page is such a big deal, or such a hard thing to do.
edit: BTW Neobond, the links are still a little wrong. The "Firefox 2.0 RC2 for <operating system> (English)" links don't point directly to an .exe (like they did before) and the 'Other languages' for Windows link is malformed
Um, no. This is a release candidate for the final release. The 2.0 Betas are over.
Will future bug fixes be backported to Firefox 1.5 or will we be forced to upgrade to Firefox 2.0 to get the bug fixes?
http://fhttp//releases.mozilla.org/pub/moz...s/2.0rc2/win32/
it should be
http://releases.mozilla.org/pub/mozilla.or...s/2.0rc2/win32/
http://www.mozilla.org/projects/bonecho/all-rc.html
That's enough info for me...
Q3? Er.. isn't that just over?
Unfortunately, the roadmap on mozilla site states the same too [worse infact, it says late Q2/early Q3]
(Im a windows user, I wouldn't know. At least for now.)
http://mirror.opensourcehub.com/pub/mozill...eleases/2.0rc2/
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.