E10s/Status/March25: Difference between revisions

E10s/Status/March25 (view source)

791 bytes removed , 25 March 2016

canmove, Confirmed users, Bureaucrats and Sysops emeriti

5,401

edits

@@ Line 10: / Line 10: @@
 ==Why yellow? e10s is designated 'yellow' or 'at risk' because: ==
-Although our release criteria has been set since December, we're finding there are enough questions on part of key teams such as release management and product management on the platform side so we're taking the time to fine-tune to be certain everyone is very confident in the POR. Additionally, although the A/B Experiment logistics and incoming data thus far is better than it has been, it's still really new. We need to be 100% certain it's valid. Additionally, we want to ensure that the improvements we may be seeing in data holds weight with users so we are spinning up efforts to make this happen (more details next week).
+Our release criteria indicates we have more work to do on the stability side. Given that we are at week 4 as of next week, our current call is that we will likely continue to do experiments in Beta 47 vs. releasing to a % of our  cohort population.
-Also, we need to flesh our a plan for our add-ons population. Although, accomodating users with add-ons is not a blocker for the initial release, it's important we have a plan because we'd like to have code land in 47, 48+ so we need to be ready. We hare getting closer, efforts on add-on compat have been steady for awhile, but we don't have a final plan of record for the client/UX part of the equation.
 ==Highlights and Accomplishments==