canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/Jan29: Difference between revisions
Jump to navigation
Jump to search
→Executive Summary
| Line 3: | Line 3: | ||
=e10s Weekly Update: '''Jan 29'''= | =e10s Weekly Update: '''Jan 29'''= | ||
==Executive Summary== | ==Executive Summary== | ||
* Plan of record is to enable e10s as of Firefox 46 (GA April 19). This initial GA release ''' | * Plan of record is to enable e10s as of Firefox 46 (GA April 19). This initial GA release '''exclude''' users with Add-Ons, users with a11y features enabled, and localized RTL language versions. We are currently determined the total number of users who will have e10s enabled in GA {{bug|1229949}}. | ||
* The team is currently focused on burning down Milestone 8 issues | * The team is currently focused on burning down Milestone 8 issues. M8 tickets block riding the trains for the above populations as of 46 Beta (March 8). M8 is largely focused on correctness, responsiveness, and stability. Velocity is high, fixed vs. incoming rate is about at stasis. | ||
conducting an A/B Telemetry in Firefox 45 Beta (Jan 27) to achieve two things: (1) determine which add-ons are causing problems with e10s so we can get prepare for (2) prove we are meeting or exceeding our release criteria for stability and responsiveness | |||
==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ||