E10s/Status: Difference between revisions

Jump to navigation Jump to search
147 bytes removed ,  6 November 2015
Line 8: Line 8:


==Exec Status==
==Exec Status==
 
*Engineering continues to burn down M8 Issues. The M8 milestone represents the completion of all functional work deemed necessary for rollout to BETA. Remaining milestone(s) will concentrate on performance work and any incoming issues.
*Engineering is burning down M8 Issues. The M8 milestone represents the completion of all functional work deemed necessary for rollout to BETA. Remaining milestone(s) will concentrate on performance work and any incoming issues.
*Content performance team has kicked off a Telemetry Experiment to conduct A/B testing as of the morning of Oct 23, see {{Bug|1193089}}. The complete study should be complete around Nov 9th.  
*Content performance team has kicked off a Telemetry Experiment to conduct A/B testing as of the morning of Oct 23, see {{Bug|1193089}} . It will run this last week of Aurora 43.0. The complete study should be complete around Nov 9th. Data has already trickled in and we will be sharing interesting learnings iteratively as analysis takes place.
*Add-on compatibility continues to be a primary focus with details available, here. Criteria for Add-Ons has been set. We need to decide what the UX will be for both general add-ons use cases and for slow add-on warnings, specifically.
*Add-on compatibility continues to be a primary focus with details available, here. Criteria for Add-Ons has been set. We need to decide what the UX will be for both general add-ons use cases and for slow add-on warnings, specifically.
*Automated tests: we are working with module owners to be sure their automated tests are groomed for e10s. We will be developing more milestones to track progress, soon.
*Automated tests: we are working with module owners to be sure their automated tests are groomed for e10s. We will be developing more milestones to track progress, soon.
*Accessibility: open question whether we block on accessibility compatibility. Support is preferred for simplicity but blocking on the development will impact the schedule by up to three months.
*Accessibility: open question whether we block on accessibility compatibility. Support is preferred for simplicity but blocking on the development will impact the schedule by up to three months.
*We are working on action items unearthed by our release crtieria to clear the path to a final plan of record by Nov 13th.
*We are working on action items unearthed by our release critieria to clear the path to a final plan of record by Nov 13th.
canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401

edits

Navigation menu