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.
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?u... 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.
> 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.
> 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?u... > 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.
> Axel
> On 15.03.11 18:51, Damon Sicore wrote: >> All,
>> 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.
> 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?u... > 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)
What do you mean by "be better now than when we did RC1"? Were they not included in RC1, or did they improve their strings?
>> 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) > What do you mean by "be better now than when we did RC1"? Were they not > included in RC1, or did they improve their strings?
Improved their strings, the only new locale would be Vietnamese.
>> 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.
>> Axel
>> On 15.03.11 18:51, Damon Sicore wrote: >>> All,
>>> 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.
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 <l...@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?u... 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.
> Axel
> On 15.03.11 18:51, Damon Sicore wrote:
>> All,
>> 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.
> On 15/03/11 18:54, Armen Zambrano Gasparnian wrote: >> The automation is not as flexible and it has not been done before. >> It would be manual for most parts.
> Could we do it for just .vi? I.e. 3 builds, manually?
> 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".
> On 16/03/11 16:19, Ben Hearsum wrote: >> 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. > 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".
> Gerv
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 Wed, Mar 16, 2011 at 12:30 PM, Ben Hearsum <bhear...@mozilla.com> wrote: > On 03/16/11 12:23 PM, Gervase Markham wrote:
>> On 16/03/11 16:19, Ben Hearsum wrote:
>>> 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.
>> 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".
>> Gerv
> 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.
I'm not exactly sure what the plans are. If we're not doing a 4.0.1 at all, that changes the equation a bit, but I still fall in favour of leaving out .vi for the same reasons. In any case, release drivers will be making the call.
> Is there going to be a 4.0.1? My (very limited) understanding is that there > are no plans for a 4.0.1 short of a chemspill.
> - Kyle
> On Wed, Mar 16, 2011 at 12:30 PM, Ben Hearsum<bhear...@mozilla.com> wrote:
>> On 03/16/11 12:23 PM, Gervase Markham wrote:
>>> On 16/03/11 16:19, Ben Hearsum wrote:
>>>> 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.
>>> 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".
>>> Gerv
>> 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.
I'm not exactly sure what the plans are. If we're not doing a 4.0.1 at all, that changes the equation a bit, but I still fall in favour of leaving out .vi for the same reasons. In any case, release drivers will be making the call.
> Is there going to be a 4.0.1? My (very limited) understanding is that there > are no plans for a 4.0.1 short of a chemspill.
> - Kyle
> On Wed, Mar 16, 2011 at 12:30 PM, Ben Hearsum<bhear...@mozilla.com> wrote:
>> On 03/16/11 12:23 PM, Gervase Markham wrote:
>>> On 16/03/11 16:19, Ben Hearsum wrote:
>>>> 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.
>>> 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".
>>> Gerv
>> 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.
> Is there going to be a 4.0.1? My (very limited) understanding is that there > are no plans for a 4.0.1 short of a chemspill.
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 3/16/11 9:41 AM, Kyle Huey wrote: >> Is there going to be a 4.0.1? My (very limited) understanding is that there >> are no plans for a 4.0.1 short of a chemspill.
> 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. ;)
> There is a meeting coming out on this very point today. Hold tight.
> Christian
> On Mar 16, 2011, at 1:36 PM, Justin Dolske wrote:
>> On 3/16/11 9:41 AM, Kyle Huey wrote: >>> Is there going to be a 4.0.1? My (very limited) understanding is that there >>> are no plans for a 4.0.1 short of a chemspill.
>> 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 Wed, Mar 16, 2011 at 9:23 AM, Gervase Markham <g...@mozilla.org> wrote: > 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".
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 world.
> On Wed, Mar 16, 2011 at 9:23 AM, Gervase Markham<g...@mozilla.org> wrote: >> 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".
> We're saying that to everyone, with many kinds of patches that affect > *all* our users.
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.
> On 16/03/11 22:18, Mike Shaver wrote: >> On Wed, Mar 16, 2011 at 9:23 AM, Gervase Markham<g...@mozilla.org> wrote: >>> 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".
>> We're saying that to everyone, with many kinds of patches that affect >> *all* our users.
> 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.
On Mar 15, 1:51 pm, Damon Sicore <dsic...@mozilla.com> wrote:
> All,
> 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,
> Damon
Hi All,
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 shipping FF
Has the memory issue with FF been resolved.. It has been known to be a memoryhog, and frankly that issue has been the biggest backdraw with FF. Other than that I am very satisfied with the browser.
