Recommended Posts

well it redirects to the coming soon page for me so cant download it yet. but here is the proof its being released today:

https://wiki.mozilla.org/Releases/Firefox_4.0rc1/BuildNotes

scroll to the bottom.. it says pushed to mirrors.

i get permission denied when trying to download it.

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

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.

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.

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
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.