Closed Bug 1340936 (win64-rollout) Opened 3 years ago Closed 2 years ago

Roll out 64-bit Firefox as the stub installer default for Win64 OS users

Categories

(Firefox :: Installer, defect)

x86_64
Windows
defect
Not set

Tracking

()

RESOLVED FIXED
Tracking Status
firefox51 --- wontfix
firefox52 --- wontfix
firefox53 --- wontfix
firefox54 --- wontfix
firefox55 --- fixed

People

(Reporter: cpeterson, Assigned: cpeterson)

References

Details

We plan to run a Funnelcake experiment (bug 1309847 and bug 1309847) in Firefox 54, comparing win64 and wow64 user metrics. If everything looks good, we will then roll out the 64-bit installer default for Win64 OS users in Firefox 55.

https://wiki.mozilla.org/Firefox/Win64#Schedule
Depends on: 1333486
Depends on: 1338170
Depends on: 1342347
Depends on: 1342690
Depends on: 1344220
No longer depends on: 1339870
No longer depends on: 1342690
No longer depends on: 1302078
Depends on: 1345649
No longer depends on: 1338170
Depends on: 1348629
So, I have a question.  Is this an issue with Win-64 or an issue that WIn-64 builds have windowless plugins disabled?  If it is the latter it would be better in trying to triage issues if it were set to block the correct bug.
I'm not sure I understand your question, but this meta bug tracks issues that prevent us from making Win64 Firefox the default for users on Win64 OS. Flash bug 1348629 is either a bug in our 64-bit NPAPI sandbox or when we force Flash async drawing. Regardless, we need 64-bit Flash to work as well as 32-bit Flash before we can make Win64 Firefox the default.
(In reply to Chris Peterson [:cpeterson] from comment #2)
> I'm not sure I understand your question, but this meta bug tracks issues
> that prevent us from making Win64 Firefox the default for users on Win64 OS.
> Flash bug 1348629 is either a bug in our 64-bit NPAPI sandbox or when we
> force Flash async drawing. Regardless, we need 64-bit Flash to work as well
> as 32-bit Flash before we can make Win64 Firefox the default.

MY question was is this a it does not work at all under wing64 or is it a thing that does not work under win64 with the default win64 does not permit windowless flash (which win32 does) if so it should be more sensible in trying to triage bugs to make this dependent on the mkae windowless flash work under win64 than having it be dependent here.  Just trying to help here.
(In reply to Bill Gianopoulos [:WG9s] from comment #3)
> (In reply to Chris Peterson [:cpeterson] from comment #2)
> > I'm not sure I understand your question, but this meta bug tracks issues
> > that prevent us from making Win64 Firefox the default for users on Win64 OS.
> > Flash bug 1348629 is either a bug in our 64-bit NPAPI sandbox or when we
> > force Flash async drawing. Regardless, we need 64-bit Flash to work as well
> > as 32-bit Flash before we can make Win64 Firefox the default.
> 
> MY question was is this a it does not work at all under wing64 or is it a
> thing that does not work under win64 with the default win64 does not permit
> windowless flash (which win32 does) if so it should be more sensible in
> trying to triage bugs to make this dependent on the mkae windowless flash
> work under win64 than having it be dependent here.  Just trying to help here.

Just trying to figure out if wee can get the dependent bugs here to follow a tree rather than just having them all be on this one.
(In reply to Bill Gianopoulos [:WG9s] from comment #3)
> MY question was is this a it does not work at all under wing64 or is it a
> thing that does not work under win64 with the default win64 does not permit
> windowless flash (which win32 does)

We don't know if bug 1348629 is win64-specific yet.

(In reply to Bill Gianopoulos [:WG9s] from comment #4)
> Just trying to figure out if wee can get the dependent bugs here to follow a
> tree rather than just having them all be on this one.

I find a deep bug tree more difficult to use because the Bugzilla does not support recursive queries and if an intermediate bug is closed, then all its children are orphaned and don't show up Bugzilla bug tree view.

A deeper bug tree would not allow me to show the tidy list of Win64 blocking bugs on the Win64 project wiki: 

https://wiki.mozilla.org/Firefox/Win64#Bugs
That is find I just thought treeing the issues would make it easier to figure out what needed to be worked on.  If it does not, I am fine with that.
My feeling was sort of if there are 5 issues that are all dependent on one thing then maybe fixing that would fix all five.  If you feel that kind of info is not useull then go forth and try to fix.
Depends on: 1334803
Depends on: 1357489
Depends on: 1354611
Depends on: 1358502
No longer depends on: 1358502
Depends on: 1357218
Depends on: 1284375
Depends on: 1359506
Depends on: 1359886
Depends on: 1359443
Depends on: 1363290
Looks like it is down to 12 bugs left blocking this. I wish Firefox people could pool resources, and tackle different bug groups all in one swoop, to work on problem areas like this; instead of everybody off doing their own thing. If that is happening, is it documented anywhere? Thanks.
(In reply to Worcester12345 from comment #8)
> Looks like it is down to 12 bugs left blocking this. I wish Firefox people
> could pool resources, and tackle different bug groups all in one swoop, to
> work on problem areas like this; instead of everybody off doing their own
> thing. If that is happening, is it documented anywhere? Thanks.

We're actively working on these 64-bit bugs. The following wiki has our schedule for rolling out 64-bit to more users this year:

https://wiki.mozilla.org/Firefox/Win64#Schedule
No longer depends on: 1359506
No longer depends on: 1276558
No longer depends on: 1284375
Depends on: 1321493
Depends on: 1366756
Depends on: 1366860
Depends on: 1369351
Depends on: 1367054
Depends on: 1294602
Depends on: 1375472
No longer depends on: 1375472
Depends on: 1377555
(In reply to Worcester12345 from comment #8)
> Looks like it is down to 12 bugs left blocking this. I wish Firefox people
> could pool resources, and tackle different bug groups all in one swoop, to
> work on problem areas like this; instead of everybody off doing their own
> thing. If that is happening, is it documented anywhere? Thanks.

(In reply to Chris Peterson [:cpeterson] from comment #9)
> (In reply to Worcester12345 from comment #8)
> > Looks like it is down to 12 bugs left blocking this. I wish Firefox people
> > could pool resources, and tackle different bug groups all in one swoop, to
> > work on problem areas like this; instead of everybody off doing their own
> > thing. If that is happening, is it documented anywhere? Thanks.
> 
> We're actively working on these 64-bit bugs. The following wiki has our
> schedule for rolling out 64-bit to more users this year:
> 
> https://wiki.mozilla.org/Firefox/Win64#Schedule

Looks like it is down to 4 now.
Awesome job so far! One left.
Blocks: 1367054
No longer depends on: 1367054
64-bit is now shipping as the stub installer default in Firefox 55! \o/
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.