canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/March29: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "thumbnail|left<br> =e10s Update: '''March 29'''= ==Executive Summary== * Our current Plan of record is to continue to conduct A/B Experiments in our be...") |
No edit summary |
||
| Line 7: | Line 7: | ||
* 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 remains our central focus. | *With the approach of Firefox 47 merging to Beta on April 18, market readiness remains our central focus. Overall, the phase of the project we current is best described as Convergence. | ||
==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ==Why yellow? e10s is designated 'yellow' or 'at risk' because: == | ||
| Line 13: | Line 13: | ||
==Highlights and Accomplishments== | ==Highlights and Accomplishments== | ||
*Check out a summary of the engineering happenings | *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== | |||
* 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 the the precise tasks that need to happen prior to GA (besides M9s) | |||
* Now that we have a track back schedule, and we tightly coordinated | |||
** Track back schedule captures transitioning to beta. | |||
** Roll-Out plan (transitioning from beta to release) | |||
==Release Criteria== | |||
* | |||
==Add-Ons + WebExtensions== | ==Add-Ons + WebExtensions== | ||
| Line 46: | Line 56: | ||
|- | |- | ||
! Date !! Trunk !! Aurora !! Beta !! Release | ! Date !! Trunk !! Aurora !! Beta !! Release | ||
|- | |- | ||
| 3-07 || 48 default (release criteria driven) || 47 default || 46 A/B || 45 off | | 3-07 || 48 default (release criteria driven) || 47 default || 46 A/B || 45 off | ||