E10s/Status/March25: Difference between revisions

Jump to navigation Jump to search

E10s/Status/March25 (view source)

Revision as of 21:34, 25 March 2016

242 bytes added ,  25 March 2016
→‎Executive Summary
Line 3: Line 3:
=e10s Weekly Update: '''March 25'''=
=e10s Weekly Update: '''March 25'''=
==Executive Summary==
==Executive Summary==
* Our current Plan of record to enable e10s as of Firefox . This initial GA release will be a cohort release targeting 100% of users '''without''' Add-Ons, users '''without''' a11y features enabled, and, the non-RTL language versions of Firefox. Talk about release criteria here.  
* Our current Plan of record is to continue to conduct A/B Experiments in our beta channel until we can [https://bugzilla.mozilla.org/show_bug.cgi?id=1259512 lower our rate of content process and Plugin crashes]. Our latest A/B experiment derived data set indicates we have work to do on stability before we're ready to ship to beta. We are, however, hitting our goals in many areas of our [https://wiki.mozilla.org/Electrolysis/Release_Criteria release criteria] such as Page Load, Startup/Shutdown time, and Scrolling. We still have work to do in areas such as UI Smoothness, Plugin Jank, Memory Usage, and GFX performance. We have made excellent progress in our cadence of deploying A/B experiments and quickly ascertaining the data so we have hit a place where we are tightly coordinated and people are moving on issues swiftly. Another important thing to note is that we are currently using the System Add-On to deploy our A/B experiments so we are testing the mechanism we designed to ship e10s rather than using experiment code.


* The has shifted to burning down M9's [https://wiki.mozilla.org/E10s/Status/m9]. M9 tickets block riding the trains for the above populations for GA. M9 is focused on fixing issues derived from our Telemetry A/B experiments such as top crashes, regressions, and backlog items deemed to be blockers by product.  
* The team has shifted to burning down M9's [https://wiki.mozilla.org/E10s/Status/m9]. M9 tickets need to hit zero before we're ready to do our cohort release for GA. M9 is focused on fixing issues derived from our Telemetry A/B experiments such as top crashes, regressions, and backlog items deemed to be blockers by product. We have hit a stage where a portion of the M9's are the responsibility of teams outside of the e10s team so we will be rolling those tickets into central triage managed by RelMan to help with load balance.  


*We have hid stride with Telemetry data from the Firefox 45 Beta experiment to help us evaluate readiness for ; initial data indicates we are in good shape in terms of jank {{Bug|1223780}}. Though, we need to continue to confirm this data is valid, especially during the second phase of Beta 45 A/B testing. We also are getting help from platform product to audit our current set of [https://docs.google.com/document/d/1kdYHycZN1ETRcw3B3xH4fnNnAs4dzRh3loUX9x8UhZQ/edit performance criteria] and help us get a plan in place to manually validate this data in order to confirm that positive data is equivalent to a positive user experience in the real world.
*With the approach of Firefox 47 merging to Beta on April 18, market readiness remains our central focus.
 
*With the approach of Firefox 46 merging to Beta on March 7, market readiness becomes a central focus. We're kicking off an e10s Cross-Functional weekly meeting as of Friday, Feb 19.


==Why yellow? e10s is designated 'yellow' or 'at risk' because: ==
==Why yellow? e10s is designated 'yellow' or 'at risk' because: ==
ErinL ancaster
canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1124250"

Navigation menu