Meet Firefox 4.0.1


Recommended Posts

How's that possible?

canweshipyet still shows 1 blocker left.

Because it's an RC1, and the blocker (I believe) is server-side, so doesn't actually need an RC2.

Link to comment
Share on other sites

RC1 will be published to the beta audience as soon as QA signs off on it (today or tomorrow, most likely)

? so far, no showstoppers have been found, and no need for an RC2 has been identified

? QA has requested more time for thorough testing, so expect at least 1-2 more weeks before final ship

? please note that as of tomorrow desktop nightly builds will no longer be identical to RC1 and in fact will contain code that is not planned on being part of Firefox 4 for Windows, Mac or Linux (see below)

https://wiki.mozilla.org/Firefox/Planning/2011-03-09

  • Like 2
Link to comment
Share on other sites

RC1 will be published to the beta audience as soon as QA signs off on it (today or tomorrow, most likely)

? so far, no showstoppers have been found, and no need for an RC2 has been identified

? QA has requested more time for thorough testing, so expect at least 1-2 more weeks before final ship

? please note that as of tomorrow desktop nightly builds will no longer be identical to RC1 and in fact will contain code that is not planned on being part of Firefox 4 for Windows, Mac or Linux (see below)

https://wiki.mozilla.org/Firefox/Planning/2011-03-09

Good news.

Link to comment
Share on other sites

Because it's an RC1, and the blocker (I believe) is server-side, so doesn't actually need an RC2.

I was under the impression Mozilla branded a build a "release candidate" only after all blockers were patched... although I agree the last blocker is not that big a deal.

I wonder what the deal is with this "test day"... I thought that it would be the rigorous QA.

Link to comment
Share on other sites

Unable to check right now, but is the final RC1 build the same as build 1?

from what everyone is saying, yes it is

Link to comment
Share on other sites

I was under the impression Mozilla branded a build a "release candidate" only after all blockers were patched... although I agree the last blocker is not that big a deal.

I wonder what the deal is with this "test day"... I thought that it would be the rigorous QA.

The blocking bug is a non-code bug though, meaning it has no affect over the actual compiled code when it's fixed (similar to the blocking bug for updating the website)

  • Like 2
Link to comment
Share on other sites

In the addons manager, when I double click on the default theme, it shows the Firefox 3.x icons... WTF?!

Well whaddya know ... you're right. Woops :p

Not like it really affects anything, but I guess it was just never updated.

Link to comment
Share on other sites

In the addons manager, when I double click on the default theme, it shows the Firefox 3.x icons... WTF?!

also the library looks really out-of-date

Link to comment
Share on other sites

YES final rc is same filesize as build 1.

The Official RC is build one. So if you downloaded it from:

http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0rc1-candidates/build1/win32

You are using the Officiall RC1

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.