canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
No edit summary |
|||
| Line 42: | Line 42: | ||
**'''We will NOT block on WebExtensions'' for any GA plans | **'''We will NOT block on WebExtensions'' for any GA plans | ||
**'''We DO need to figure out what the product requirements are''', if any for UX relating to Add-ons in an e10s world in general. This also coincides with the Shield project. UX, and Perf are engaged and we're starting conversations about user interaction and API readiness. | **'''We DO need to figure out what the product requirements are''', if any for UX relating to Add-ons in an e10s world in general. This also coincides with the Shield project. UX, and Perf are engaged and we're starting conversations about user interaction and API readiness. | ||
==Automated tests== | ==Automated tests== | ||
| Line 54: | Line 49: | ||
https://public.etherpad-mozilla.org/p/e10stests-taskforce | https://public.etherpad-mozilla.org/p/e10stests-taskforce | ||
==A11y== | |||
** Wiki to track work is, [https://wiki.mozilla.org/Accessibility/Electrolysis2 here]. | |||
** '''Decision made to not block going to GA''' on A11y. We are ramping up to help be sure we do everything we can to get a good level of parity. | |||
** We are planning on getting e10s team + Firefox functional teams together in Orlando to continue the envangelize pruning and greening up of tests on part of module owners. | |||
==Release Schedule== | ==Release Schedule== | ||
Currently Proposed Schedule is to enable e10s by default for Users without Add-Ons for 45.0 and target a larger population for 46.0. As mentioned above, we'll do a go/no-go on the 28th of Dec. | Currently Proposed Schedule is to enable e10s by default for Users without Add-Ons for 45.0 and target a larger population for 46.0. As mentioned above, we'll do a go/no-go on the 28th of Dec. | ||