|
|
| Line 10: |
Line 10: |
|
| |
|
| ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == |
| Incoming data from our latest A/B experiment indicates we have more work to do on the stability side. Given that we are at week 4 in our dev cycle leading to Firefox 47 beta, we will likely continue to do experiments in Beta 47 vs. releasing to a % of our cohort population. | | Incoming data from our latest A/B experiment indicates we have more work to do on the stability side. We also need to tighten up how we are operating by increasing fidelity of our stability data and and reducing latency to measure progress as much as we can. |
|
| |
|
| ==Highlights and Accomplishments==
| |
| *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]
| |
| *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 | | * 04/13: e10s stability task force checkpoint |
| * 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) | | * 04/15: lock on final plan for Firefox 47 beta |
| * Now that we have a [https://docs.google.com/spreadsheets/d/101ra3HjqyufjP79JkGa4e0RyHPLVlJXS43rXtKuoJw4/edit#gid=0 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
| | |
| * We will be reaching out to module owners to sign off on their efforts to fix automated tests in the next week
| |
|
| |
|
| ==Release Criteria== | | ==Release Criteria== |