Confirmed users
471
edits
| Line 38: | Line 38: | ||
** Panel API (myk): has WIP patch, mostly complete. Needs tests+docs. Needs E10S-compliancing. Should have ready for review by next week (except for E10S compliance). On-track. | ** Panel API (myk): has WIP patch, mostly complete. Needs tests+docs. Needs E10S-compliancing. Should have ready for review by next week (except for E10S compliance). On-track. | ||
** Request API (paul): myk will ping paul for status | ** Request API (paul): myk will ping paul for status | ||
*** has some tests, needs mock-XHR for tests | |||
** app compatibility handling (atul): Luca submitted a patch, still r?=atul, sits below E10S stuff on atul's queue. | ** app compatibility handling (atul): Luca submitted a patch, still r?=atul, sits below E10S stuff on atul's queue. | ||
** lifecycle (adw): on-track. Has WIP patch. Wants comments on the API (use of 'self' module) | ** lifecycle (adw): on-track. Has WIP patch. Wants comments on the API (use of 'self' module) | ||
| Line 43: | Line 44: | ||
** Selection API (erik): new patch posted yesterday, waiting for r?=myk | ** Selection API (erik): new patch posted yesterday, waiting for r?=myk | ||
** SDK search path (?): no progress. Atul can take it as P2. New definition of deliverable is to merely specify the current behavior, not try to change it at all. on-track. | ** SDK search path (?): no progress. Atul can take it as P2. New definition of deliverable is to merely specify the current behavior, not try to change it at all. on-track. | ||
** flightdeck | * flightdeck | ||
** freeze is next week (tuesday june 8th), RC jun09, final jun16 | |||
** piotr is missing, some status second-hand through dbuc | |||
*** oscar is cranking on UX stuff this week, done with switching module view mode, has read-only bespin and view mode done, working on new module creation now | |||
*** working on XPI creation? | |||
** improvements to flightdeck addon (atul): will figure out offline w/myk | |||
** step-by-step tutorial (atul): blocked on new version of frontend | |||
* platform dependency brainstorming | |||
** dependencies quietly crop up | |||
** want/need involvement from platform team to avoid/fix | |||
* roundtable | |||
** security testing? what sorts of security review can be done in parallel with development? suggested API review, mostly on the mozilla-labs-jetpack discussion group | |||
= Followups = | = Followups = | ||