Firefox/AddOns/Status/20150813: Difference between revisions

full status report for addons week of aug 13
(status for august 12)
 
(full status report for addons week of aug 13)
Line 2: Line 2:


== Overall Project Health - YELLOW ==
== Overall Project Health - YELLOW ==
* Add-On Signing is now live in 41 beta, removal of the about:config override preference slated for 42 (excluding ESR and Dev Edition)
* Significant progress, significant concerns. See summary and risks below.  
* e10s ...?
* Web Extensions .. ?
* other?


== Exec Summary ==
== Exec Summary ==
* Signing client work and AMO side work is done, validator improvements are moving forward but progress is not rapid.  
* Add-On Signing: is now live in 41 beta, removal of the about:config override preference slated for 42 (excluding ESR and Dev Edition)
* Full Add-On ecosystem strategy has been developed but is not yet resourced and therefore is on hold.
* e10s: e10s will ship in 42 Aurora. Add-on compatibility testing efforts continue to be maintained at http://arewee10syet.com/  Earliest e10s will ship in release is 43.
* WebExtensions: Extension API landed on Nightly. https://wiki.mozilla.org/WebExtensions has details.
* AMO further roadmap development is on hold pending resourcing.  


== Risks/Issues ==
== Risks/Issues ==
Line 15: Line 14:
* Unlisted addons considered critical are being reviewed as soon as they are submitted (unlisted queue is under control) but many unlisted addon developers have not (or are presumed to have not) yet submitted for review.  
* Unlisted addons considered critical are being reviewed as soon as they are submitted (unlisted queue is under control) but many unlisted addon developers have not (or are presumed to have not) yet submitted for review.  


* Review Queue - we have insufficient resources for the listed review queue which is very long and growing. We recently hired one new FTE, but also have had to move one reviewer over to working on the validator improvements. We do have budget for a part time contract reviewer, and that search is moving quickly.  
* Review Queue - we have insufficient resources for the listed review queue which is very long and growing. We recently hired one new FTE, but also have had to move one reviewer over to working on the validator improvements. We do have budget for a part time contract reviewer, and a candidate has been selected. Review queue challenges illustrated here: http://diox.github.io/amo-review-times/  
 
* Validator - the validator has several issues slowing down the queue - it is not providing very useful results to developers, and it is rejecting 4/5 addons. We have a roadmap for it in development, 3 developers assigned to improvements now and have just established weekly status/triage sessions for it.


* Validator - the validator has several issues slowing down the queue - it is not providing very useful results to developers, and it is rejecting 4/5 addons. We have a roadmap for it in development, 2 FTE assigned to improvements, and the first phase of these is nearly complete.


== Accomplished for Week ==
== Accomplished for Week ==
Line 26: Line 24:
== Planned for Upcoming Week ==
== Planned for Upcoming Week ==
* test validation of known malevolent add-ons
* test validation of known malevolent add-ons
* cross coordination of signing and e10s related addon issues
* further establishment of full add-ons "program"
* progress on getting more reviewers onto the queue
* progress on getting more reviewers onto the queue, both volunteer and staff


== Important Links/References ==
== Important Links/References ==
* Case for Extension signing: https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/
* Case for Extension signing: https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/
*
* WebExtensions:
* Review queue time data: http://diox.github.io/amo-review-times/
Confirmed users
613

edits