This bug is not the place to argue about this decision, which has already been made. * disable the win64 option in try/trychooser * stop doing win64 “hourly” builds on mozilla-central and other branches * repatriate existing win64 nightly users onto win32 builds using a custom update This includes the following subtasks, which I’m not filing specific bugs on but you may want to break these out:
Please stop building windows 64 builds and tests.
He then went and posted this note over on Bugzilla: Please let us consider this discussion closed unless there is critical new information which needs to be presented. Given the existing information, I have decided to proceed with disabling windows 64-bit nightly and hourly builds. Thank you to everyone who participated in this thread. Yet Smedberg had clearly already made up his mind, as he finally declared: Some were for it, but most were against the discontinuation. We basically ignore a set of nightly “topcrashes” because they are 64-bit only. It is also frustrating for stability team triage because crash-stats does not easily distinguish between 32-bit and 64-bit builds in the topcrash lists and other reports.This is frustrating for users because they feel (and are!) second-class.Crashes submitted by 64-bit users are currently not high priority because we are working on other things.
The plugins that are available don’t work correctly in Firefox because we haven’t implemented things like windowproc hooking, which means that hangs are more common.Many plugins are not available in 64-bit versions.Mozilla’s manager listed the following reasons as to why the nightly builds should get the axe: Mozilla Engineering Manager Benjamin Smedberg last Friday quietly posted a thread over on the Google Groups discussion board titled “Turning off win64 builds.” By Wednesday, Smedberg had declared that the 64-bit version of Firefox for Windows would never see the light of day, unless Mozilla decides to revert the decision at some point in the future.
0 kommentar(er)
