Firefox/AddOns/Status/current: Difference between revisions

Line 436: Line 436:
|-
|-
| align="left"| After releasing many new API's in Fx48, we are finding and fixing bugs - which has slowed down some of our initial goals (some that we had hoped to land in Fx50 are more Fx51).
| align="left"| After releasing many new API's in Fx48, we are finding and fixing bugs - which has slowed down some of our initial goals (some that we had hoped to land in Fx50 are more Fx51).
| '''Open'''
| '''Closed'''
| Andym
| Andym
| Fx51
| Fx51
Line 443: Line 443:
|-
|-
| align="left"| Focus on e10s impacting work may make us prioritize some complex APIs used by a few widely adopted add-ons, rather than addressing some of the broader adoption and simpler APIs as quickly as we want.  Currently at risk is Permissions.
| align="left"| Focus on e10s impacting work may make us prioritize some complex APIs used by a few widely adopted add-ons, rather than addressing some of the broader adoption and simpler APIs as quickly as we want.  Currently at risk is Permissions.
| '''Open'''
| '''closed'''
| Andym
| andy
| Fx51
| Fx51-54
| align="left"| There really isn't a mitigation to this oneIt will impact if issues trump current work.
| align="left"| Permissions moved out 2 releases.  only enabling SDK tests that work - disabling rather than fixing others.  Months of work to fix SDK tests in Try would have traded off for web development tools (not good bargain over next few months).  Implementing more metrics in Beta (for hangs) and continuing to monitorSeveral high impact fixes to SDK in performance that reduced hangs and hang length significantly.
|
|
|-
|-
Confirmed users
1,094

edits