Firefox/Win64: Difference between revisions
(→Release Criteria: Link to Firefox 53 dashboard) |
|||
| Line 21: | Line 21: | ||
** {{mdone|}} '''October 7''' - Web team will complete A/B test of new download page. | ** {{mdone|}} '''October 7''' - Web team will complete A/B test of new download page. | ||
** {{mdone|}} '''October''' - Drop support for non-Flash NPAPI plugins in Nightly 52. ({{bug|1269807}}) | ** {{mdone|}} '''October''' - Drop support for non-Flash NPAPI plugins in Nightly 52. ({{bug|1269807}}) | ||
** {{ | ** {{mdone|}} '''October''' - Create [https://sql.telemetry.mozilla.org/dashboard/win64-indicators dashboards for 64-bit rollout criteria]. | ||
** {{ | ** {{mdone|}} '''November 24''' - Make 64-bit Firefox the default in the stub installer for all eligible users in Nightly 53. ({{bug|797208}}) | ||
** {{mok|}} ''' | ** {{mdone|}} '''November 7''' - Start of Nightly 53 development cycle. | ||
** {{ | ** {{mok|}} '''December''' - Fix [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&status_whiteboard=sbwn1&resolution=---&query_format=advanced Flash sandbox bugs]. | ||
** {{mrisk|}} '''December''' - Announce ctypes deprecation. | |||
** {{mrisk|}} '''December''' - [https://github.com/mozilla/amo-validator/issues/467 Forbid ctypes in AMO's add-on validator] (for Firefox 52?) | ** {{mrisk|}} '''December''' - [https://github.com/mozilla/amo-validator/issues/467 Forbid ctypes in AMO's add-on validator] (for Firefox 52?) | ||
* '''2017 Q1''' | * '''2017 Q1''' | ||
| Line 31: | Line 31: | ||
** {{mprop|}} '''March''' - Run [https://docs.google.com/document/d/139X1Xm0F8mjPsHPENG9r8Tofpg3lNyLp9tJUwYbeed8/ Funnelcake test] to compare 32-bit vs 64-bit for eligible Release 52 users. | ** {{mprop|}} '''March''' - Run [https://docs.google.com/document/d/139X1Xm0F8mjPsHPENG9r8Tofpg3lNyLp9tJUwYbeed8/ Funnelcake test] to compare 32-bit vs 64-bit for eligible Release 52 users. | ||
* '''2017 Q2''' | * '''2017 Q2''' | ||
** {{mok|}} '''April 18''' - Firefox 53 release '''(with | ** {{mok|}} '''April 18''' - Firefox 53 release '''(with 64-bit default)'''. | ||
** {{mprop|}} '''April''' - Announce 64-bit default for new installs for Firefox 53. | ** {{mprop|}} '''April''' - Announce 64-bit default for new installs for Firefox 53. | ||
** {{mprop|}} Google to migrate 32-bit Chrome users to 64-bit? | ** {{mprop|}} Google to migrate 32-bit Chrome users to 64-bit? | ||
Revision as of 18:25, 30 November 2016
Objective
Make 64-bit Firefox the default version for new and existing eligible users to reduce our OOM crash rate, increase performance, and improve security (ASLR).
Users are eligible for a 64-bit default if they are running 64-bit Windows 7+. 32-bit Firefox running on 64-bit Windows can access about 3,800 MiB of virtual address space (4 GiB minus overhead from physical memory reserved for the OS and BIOS). For users with less than 4 GiB of physical memory, there is a trade-off between the larger virtual address space and the overhead of 64-bit code. We have decided to remove any minimum memory requirement for 64-bit Firefox because we don't want to withhold the security benefits of ASLR. Also, 2 GiB RAM is Microsoft's minimum memory requirement for Windows 7 through 10.
Schedule
- 2015 Q2
- [DONE] May 4 - Firefox 41 - Drop support for binary XPCOM components.
- 2015 Q4
- [DONE] October 8 - Announced NPAPI to be removed by end of 2016: NPAPI Plugins in Firefox.
- [DONE] December 15 - Firefox 43 - Release 64-bit Firefox builds.
- 2016 Q3
- [DONE] July 20 - Announced NPAPI to be removed in Firefox 52: Reducing Adobe Flash Usage in Firefox.
- [DONE] August 29 - Web team will start redesigning download page redesign for 64-bit.
- [DONE] September 12 - Start of Nightly 52 development cycle.
- [AT RISK] September 23 - Web team will complete redesign of download page.
- [DONE] September 23 - Web team will start A/B test of new download page.
- 2016 Q4
- [DONE] October 7 - Web team will complete A/B test of new download page.
- [DONE] October - Drop support for non-Flash NPAPI plugins in Nightly 52. (bug 1269807)
- [DONE] October - Create dashboards for 64-bit rollout criteria.
- [DONE] November 24 - Make 64-bit Firefox the default in the stub installer for all eligible users in Nightly 53. (bug 797208)
- [DONE] November 7 - Start of Nightly 53 development cycle.
- [ON TRACK] December - Fix Flash sandbox bugs.
- [AT RISK] December - Announce ctypes deprecation.
- [AT RISK] December - Forbid ctypes in AMO's add-on validator (for Firefox 52?)
- 2017 Q1
- [ON TRACK] March 7 - Firefox 52 release.
- [PROPOSED] March - Run Funnelcake test to compare 32-bit vs 64-bit for eligible Release 52 users.
- 2017 Q2
- [ON TRACK] April 18 - Firefox 53 release (with 64-bit default).
- [PROPOSED] April - Announce 64-bit default for new installs for Firefox 53.
- [PROPOSED] Google to migrate 32-bit Chrome users to 64-bit?
- 2017 H2
- [PROPOSED] Migrate existing eligible 32-bit Firefox users to 64-bit. (bug 1274659)
- [PROPOSED] Make Flash click-to-play. (bug 1317856)
Release Criteria
- Funnelcake Win64 indicators dashboard
- Firefox 53 Win64 indicators dashboard
- Win64 active ticks should be greater than or equal to WOW64
- Win64 total URIs loaded should be greater than or equal to WOW64
- Win64 total domains loaded should be greater than or equal to WOW64
- Win64 total tabs opened should be greater than or equal to WOW64
- Win64 crash rate should be less than or equal to WOW64
- Win64 engagement ratio should be greater than or equal to WOW64 engagement ratio (TODO: copy e10s dashboard)
- Win64 performance benchmarks should be faster than or equal to WOW64
Links
- Meeting notes
- Trello board
- Stub Installer test plan
- % Win32/WOW64/Win64 Firefox users:
- Proportion of Win64 OS users by RAM:
- > 3 GiB = 91.21%
- > 3.8 GiB = 80.73%
- > 4 GiB = 37.86%
- Graph
- Chrome's 64-bit announcements: Mac and Windows (August 2014)
Bugs
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Team
| Role | Contact |
|---|---|
| Product Management | Romain Testard |
| Engineering | David Parks (Flash sandbox), Matt Howell and Robert Strong (installer), Stéphanie Ouillon (Flash sandbox review) |
| QA | Ryan VanderMeulen |
| UX | Michael Verdi (Firefox), Jon Petto (Mozilla.org) |
| Release Management | Sylvestre Ledru |
| Release Engineering | Chris AtLee |
| Firefox Program Management | Chris Peterson |
| Mozilla.org Program Management | Jennifer Bersch |
| Add-ons | Jorge Villalobos |