canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/March29: Difference between revisions
Jump to navigation
Jump to search
→e10s Update: March 29
| Line 3: | Line 3: | ||
=e10s Update: '''March 29'''= | =e10s Update: '''March 29'''= | ||
==Executive Summary== | ==Executive Summary== | ||
* Overall, the phase of the project we currently in is best described as Convergence. For Firefox 47, the most likely scenario will be that we 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 main process, content, 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 but not to the level that would necessarily block beta. 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 empowered with the right data to move 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. | * Overall, the phase of the project we currently in is best described as Convergence. For Firefox 47, the most likely scenario will be that we 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 main process, content, 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 but not to the level that would necessarily block beta. 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 empowered with the right data to move 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 current experiment (add-ons + ally = no, apz= yes) will end later this week, in time for Beta 7 and we will have updated results soon thereafter. | ||
* 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. | * 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. | ||
*With the approach of Firefox 47 merging to Beta on April 18, market readiness | *With the approach of Firefox 47 merging to Beta on April 18, quality and market readiness remain our central focus. | ||
==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ||
| Line 14: | Line 14: | ||
==Highlights and Accomplishments== | ==Highlights and Accomplishments== | ||
*Check out a summary of the engineering happenings last week: https://wiki.mozilla.org/Electrolysis/Meetings/2016-03-24 | *Check out a summary of the engineering happenings last week: https://wiki.mozilla.org/Electrolysis/Meetings/2016-03-24 | ||
*We've also made great progress fixing automated tests; by early next week we will have [https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit#gid=1558085802 owners for all tests] | *We've also made great progress fixing automated tests; by early next week we will have [https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit#gid=1558085802 owners for all tests] | ||
*WIP: manual test plan. Manual testing has been ongoing, this new test plan has new layout that is easier to follow along with risk commentary, etc. More to share soon on that. | *WIP: manual test plan. Manual testing has been ongoing, this new test plan has new layout that is easier to follow along with risk commentary, etc. More to share soon on that. | ||
==Next Steps== | ==Next Steps== | ||
* The main and content process crashes are well-documented. Next, we need to dig into the plugin crashes | * The main and content process crashes are well-documented. Next, we need to dig into the plugin crashes | ||
* Triage the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1198187&hide_resolved=1 RC Blocker Meta dependency tree] to identify | * Triage the [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1198187&hide_resolved=1 RC Blocker Meta dependency tree] to identify other tasks that need to happen prior to GA (besides M9s) | ||
* Now that we have a track back schedule, | * Now that we have a track back schedule which articulates what we need to accomplish in preparation for beta, we need to now create a precise roll-out plan. We should have something to share the week of April 7 | ||
==Release Criteria== | ==Release Criteria== | ||