Firefox 4 RC1 has received a very warm welcome; it's time to make a decision to ship. As of now, there are no known issues that would stop us from shipping RC1 as final. At the conclusion of our regular 11:30AM triage session on Wednesday, March 16th, release drivers will decide whether to ship RC1 as Firefox 4.
March 22nd is the day we would ship. Both IT and Marketing have indicated that March 22nd is an acceptable final launch date. If at any time we discover issues that would block final release, we would issue an RC2 as soon as possible, reset the ship date, and communicate to everyone.
All my best,
For one, we'd be able to take Vietnamese now, which landed just shortly
after RC, for 500k ADUs (en-US has 1M in Vietnam).
There are some 24/25 other localizations that'd be better now than when
we did RC1.
has links to the individual diffs if anyone feels really curious, but
all of them got source-review by me. (25 is Hungarian that could take
some search engine fixes)
Can't comment on what doing such an RC2 would mean for the release at large.
Improved their strings, the only new locale would be Vietnamese.
I don't plan on the existance of 4.0.1, really. Also, there's pushback
on taking l10n changes in particular on chemspills.
I'd guess we could phrase that as "we can make us take those for 4.0.1".
I don't think Damon's email was an invitation to start expressing
reasons to do an RC2. The right way to address those concerns is to:
- file a bug and nominate it by setting blocking2.0 to "?"
- hop into #planning on irc.mozilla.org and find a driver
- email release-drivers@ with your concern
On Tue, Mar 15, 2011 at 2:14 PM, Axel Hecht <l1...@mozilla.com> wrote:
> For l10n, an RC 2 would be useful.
> For one, we'd be able to take Vietnamese now, which landed just shortly
> after RC, for 500k ADUs (en-US has 1M in Vietnam).
> There are some 24/25 other localizations that'd be better now than when we
> did RC1.
> https://l10n-stage-sj.mozilla.org/shipping/about-milestone/fx4.0rc2?updated-facet=fx4.0rc1has links to the individual diffs if anyone feels really curious, but all of
> them got source-review by me. (25 is Hungarian that could take some search
> engine fixes)
> Can't comment on what doing such an RC2 would mean for the release at
> On 15.03.11 18:51, Damon Sicore wrote:
>> Firefox 4 RC1 has received a very warm welcome; it's time to make a
>> decision to ship. As of now, there are no known issues that would stop us
>> from shipping RC1 as final. At the conclusion of our regular 11:30AM triage
>> session on Wednesday, March 16th, release drivers will decide whether to
>> ship RC1 as Firefox 4.
>> March 22nd is the day we would ship. Both IT and Marketing have indicated
>> that March 22nd is an acceptable final launch date. If at any time we
>> discover issues that would block final release, we would issue an RC2 as
>> soon as possible, reset the ship date, and communicate to everyone.
>> All my best,
Could we do it for just .vi? I.e. 3 builds, manually?
My stats (albeit with the usual caveats) show it's a major locale -
1.32% of the world's internet population speaks Vietnamese:
I don't think a final release is the place for us to be doing manual,
error prone hackery like this. I'm strongly against doing this.
If you only spoke Vietnamese, you might think differently :-)
I'm not saying we need to rush to do it in time for the release on March
22nd - we can take our time, and get the .vi community to test it for
us. We could even release it as "beta" language, as I believe we have
done for some languages in previous releases - a separate section at the
bottom of the download page.
I'm just saying that for 1.32% of the world/500K ADUs, however you want
to put it, plus the big efforts of the .vi l0n team, we should be able
to do _something_ more than just say "sorry, guys, your l10n team was a
day late so now you have to wait for Firefox 5".
I didn't say we had to wait until 5. Adding it in 4.0.1 is perfectly
fine with me.
I'm against doing it in 4.0 because we have no experience adding a
locale at this point in a release, from a RelEng standpoint. We have no
ideas what the gotchas are, or what things it will cause issue with in
subsequent point releases. A final release is tricky and complicated
enough without adding in this unknown.
We are working on making late-stage locale additions possible, but
currently, it's not.
On 03/16/11 12:41 PM, Kyle Huey wrote:
My understanding is that Firefox 4 will follow the same
stability/security point-release process as Firefox 3.6 did. As such,
there will be a Firefox 4.0.1 at some point after 4.0 is released.
But AFAIK there isn't a specific schedule for it yet, other than the
usual 6 week (or whatever it was) cadence we've previously targeted for
.x updates. (Or, more bluntly, we're not cheating the 4.0 release by
having a quick 4.0.1 instead of holding 4.0. ;)
On Mar 16, 2011, at 1:43 PM, Christian Legnitto wrote:
> There is a meeting coming out on this very point today. Hold tight.
> On Mar 16, 2011, at 1:36 PM, Justin Dolske wrote:
We're saying that to everyone, with many kinds of patches that affect
*all* our users. It's not a "day late", RC was frozen many days ago.
Firefox 5 will be in ~3 months, people can wait and make sure their
strings are updated for a smaller release. It's not the end of the
The difference here from taking "just one more patch" is that the risk
of doing special builds it is limited only to the .vi users actually
using them. The release can go ahead exactly as planned.
> It's not a "day late", RC was frozen many days ago.
To be clear, by "a day late", I was referring to a statement of Axel's
where he said that the .vi team missed the deadline for RC1 by 1 day. I
wasn't suggesting that now is only 1 day late.
To clarify, as it was me that spread that data point.
vi was actually a week late with sign-off, a day late with trying to
land. bug 469634 said that they can't push on RC build date, bug 640111
was fixed on RC release date only. Sign-off on the tested localization
post the landing that day came in March 10th.
Not that that has a lot of impact on the outcome here at this point.
1 - Printing from FF4 was not successful for irctc.co.in. This was
working fine in FF3.6. Would you kindly look into this?
2 - Please keep the "Feedback" button in the release. It helps
providing feedback right from browser.
3 - Button at top left corner of firefox4 looks more beautiful by
adding the addon "Movable FF Button". Please make it inbuilt before
Yes. The memory issue with FF has been resolved. Thanks for your interest.
> There is a meeting coming out on this very point today. Hold tight.
So what's the answer?
I really, really want a 4.0.1 :-). We have lots of fixes for blocker-ish
bugs that should go into it.
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
> On Thu, Mar 17, 2011 at 9:43 AM, Christian Legnitto <cleg...@mozilla.com>wrote
>> There is a meeting coming out on this very point today. Hold tight.
> So what's the answer?
> I really, really want a 4.0.1 :-). We have lots of fixes for blocker-ish
> bugs that should go into it.
More detailed plan to follow, I believe.
Having a small issue with Firefox 4 Beta RC1, long-standing from about
Firefox 4 Beta 8-10 or something.
Each time I launch Firefox, it shows up with Restore Session, and now
with RC1 the "thanks for Downloading Firefox 4" page which only shows
up once on first launch. Issue with Restore Session is that it always
wants to restore the same session, its one from over a month ago.
Whenever I quit Firefox, even with the setting "Show my windows and
tabs from last time" it always shows Restore Session for a session
over a month old now.
Also, Firefox 4 Beta 13 had some nice changes to the back and forth
buttons, they went from circular to square with round edges, I haven't
seen that in RC1. Will we be seeing it in Firefox 5 Beta or "Firefox
With regards to the session restore issue, could you please file a bug
at the link below so we can investigate? Please give us as much detail
With regards to the back and forward buttons, these have not changed
since beta 13. If the look of your buttons have changed, it could be
due to a recent add-on, theme, or persona change. However, if there
have been no changes, you might want to file a bug on that too
Mozilla QA Engineer
Automation, Releases, and Community