E10s/Status/Jan29: Difference between revisions

E10s/Status/Jan29 (view source)

941 bytes removed , 29 January 2016

canmove, Confirmed users, Bureaucrats and Sysops emeriti

5,401

edits

@@ Line 8: / Line 8: @@
 ==Why yellow? e10s is designated 'yellow' or 'at risk' because: ==
+*Outstanding M8 tickets in progress
-#Our plan of record is solid at this point in terms of release criteria. The Product Brief is still in flight but doesn't pose risk to the project; we don't anticipate any major characteristics in terms of value proposition to shift from current understanding. At this point, that doc serves as an informational reference for cross-functional teams as they communicate "the why". The release criteria is locked down and we will be flexible in order to put quality as #1.
+*The firefox 45 A/B
-#Core team continues to working at a high velocity, we are down to [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=cf_tracking_e10s&o1=equals&resolution=---&query_based_on=e10s-m8&o2=substring&query_format=advanced&f2=status_whiteboard&v1=m8%2B&v2=e10s-m8&known_name=e10s-m8&list_id=12803370  15 open M8's].  [https://wiki.mozilla.org/E10s/Status/m8 See M8 Tracker] to get granular details on what recent things have landed in Firefox 46, what's in review, and what we've chosen is safe enough to uplift for Firefox 45.
 '''Decisions Made'''