Mozilla readies Firefox 4 Release Candidate

In a posting on Google Groups, Developer Benjamin Smedberg said in a message to fellow coders that the Mozilla developer hub was "now closed so that release engineering can prepare Firefox 4 release candidates."

And this was further confirmed when the CanWeShipYet website showed no blockers or pending patches, late last night.

Per the triage meeting today, mozilla-central is now CLOSED so that release engineering can prepare Firefox 4 release candidates. This means that NO CHANGES may land, even things which may have Firefox or Mobile
blocker flags.

Rob Sayre is preparing a plan for the mechanics of how we reopen the tree for both pending changes for Firefox Mobile 4 and new work for Firefox 5. This includes all the related details about how we manage nightly testers, branching, feature landings, and the schedule. Until this plan is finalized, the tree will remain absolutely frozen.

Please direct any followup to mozilla.dev.planning

--BDS

In what for some seemed like a long winding road, the end is finally in sight and we can all expect to see the Firefox 4 in all its glory this month.

Firefox 4, based on the Gecko 2.0 engine, will bring an updated user interface, new ways to organize tabs, a revamped add-on manager, support for HTML5 video standards, multitouch support on Windows 7 and a range of performance and security enhancements.

Don't forget that you can discuss this beta, and nightly builds right here on Neowin in the "Meet Firefox 4.0 (beta 12)" topic.

Report a problem with article
Previous Story

Massive CR-48 update lands with "fixed trackpad"

Next Story

Google implements Fragments library to combat fragmentation

61 Comments

Commenting is disabled on this article.

iAltair said,
Firefox is history.
Do you happen to have your own computer? Just wondering since remarks like that sound like you're borrowing someone else's. Stick with the subject and not appear like you're coming from far left field. Thanks.

Temuulen Battumur said,
When Mozilla will include addon sync? Because that's the one thing that I'm using Chrome.
Well storing bookmarks takes a fair amount of space of Mozilla's servers, even though Weave (Mozilla Sync or whatever its name is at the moment) is not the greatest of such services. Imagine more settings being stored for you, for free on it's servers. Mozilla can't always afford a money sink like that because it doesn't really swim in oceans of digital money like Google does. There are though free or ad supported or paid services that, at least in part support the services you want.

LauRoman said,
Well storing bookmarks takes a fair amount of space of Mozilla's servers, even though Weave (Mozilla Sync or whatever its name is at the moment) is not the greatest of such services. Imagine more settings being stored for you, for free on it's servers. Mozilla can't always afford a money sink like that because it doesn't really swim in oceans of digital money like Google does. There are though free or ad supported or paid services that, at least in part support the services you want.
They could easily use Google services (witch I'm 100% positive Google would support).

Yeah, back when they said they would ship in February... that was BS. I didn't think they could possibly make that deadline.

What happened to the Win64bit version? The last beta nightly build available is from March 1st. It is also not listed in the RC1 directory.

Gungel said,
What happened to the Win64bit version? The last beta nightly build available is from March 1st. It is also not listed in the RC1 directory.

it will come with Firefox 5 if I remember well

Gungel said,
What happened to the Win64bit version? The last beta nightly build available is from March 1st. It is also not listed in the RC1 directory.

It's part of the features that were dropped from FF4.

Aethec said,
It's part of the features that were dropped from FF4.
I'm not sure it was ever planned for Fx4. Soon after, yes.

SuperZod said,

it will come with Firefox 5 if I remember well

I wonder why they're holdling off until version 5? I would have thought 4 would be the version where you can have both 32 and 64. Oh well!

Gaffney said,
FF4 > Chrome 11 > Opera > IE9 > FF3.6
And your source is?

That's right, you don't, and not like it matters. Since just like statistics they are bent at will.

This is part of the SDLC. We create RC's, a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs.

- AaronMT (Mozilla QA Engineer)

Gutierrez said,
Release Candidate for a ****ing browser. Give me a break. Go and get a job, SLACKERS!

... Says the guy trolling in the middle of the day

Gutierrez said,
Release Candidate for a ****ing browser. Give me a break. Go and get a job, SLACKERS!

Cloud computing, never heard about this? The Browser is the new OS...

Gutierrez said,
Release Candidate for a ****ing browser. Give me a break. Go and get a job, SLACKERS!

There has been RC's for web browsers for years and not only Mozilla does it. Even MSFT does RC's. Also why don't you do your day job or go and get one rather than being being a complete looser and trolling ?

Gutierrez said,
Release Candidate for a ****ing browser. Give me a break. Go and get a job, SLACKERS!
Seriously!!!??? That's your "A" game response?

Using unsigned RC alongwith Chrome, must say very nice progress by Mozilla, release final quickly wanted to use with my new PC.

I do wish people wouldn't post direct links to Mozilla's FTP server. No need to jump the gun!
Wait until the binaries have been officially distributed among the download mirrors before
attempting to download the RC, and save the strain on Mozilla's FTP server.

DJGM said,
I do wish people wouldn't post direct links to Mozilla's FTP server. No need to jump the gun!
Wait until the binaries have been officially distributed among the download mirrors before
attempting to download the RC, and save the strain on Mozilla's FTP server.

It is there for a reason, and everyone likes new goodies. I see no issue with it. Despite the strain.

ObiWanToby said,

It is there for a reason, and everyone likes new goodies. I see no issue with it.
Despite the strain.


Mozilla certainly see an issue with it, and I'm sure AaromMT from Mozilla QA would agree
with my earlier post. The download mirrors are there for a reason. Ever heard of a thing
called "load balancing"? One other risk of jumping the gun is that even though builds
have been placed on the main Mozilla FTP server, they can still be pulled at the last
minute in case any nasty new bugs have been discovered.


It is always wise to WAIT for official availability announcements before downloading.

Well Mozillia needs to get to 2008 already and use damn bittorrent for everything instead of ftp crap!

ftp://ftp.mozilla.org/pub/firefox/nightly/4.0rc1-candidates/build1/win32/en-US/Firefox Setup 4.0 RC 1.exe

RC1 build 1, the final rc won't be labeled as rc until next week as testing of this build needs to happen first.

torrentthief said,
ftp://ftp.mozilla.org/pub/firefox/nightly/4.0rc1-candidates/build1/win32/en-US/Firefox Setup 4.0 RC 1.exe

Please don't link directly to Mozilla's FTP server as it does not have any load balancing and thus can be brought down by too many connections. If someone wishes to download the candidate build please use the HTTP link (which is load balanced):

http://ftp.mozilla.org/pub/fir.../build1/win32/en-US/Firefox Setup 4.0 RC 1.exe

sanriver12 said,

you dont get how domains work do ya?

That's 1 reason why all browsers should be highlighting/making bold "mozillla.com", so the newbies can see it better.

sanke1 said,
Are all memory leaks fixed? Beta 12 improved massively but it does feel heavy and bloaty at times. Esp on OSX.

Oooh I hope they didn't just deferred those hardblockers... I feel I have to wait for the First Firefox 4 Patch before adopting (like what I did for FF 3)

Majesticmerc said,
I think I speak for everyone here when I say:

ABOUT DAMN TIME!

Or: "Too Damn Late", back to Chrome, IE9, or Opera.