Labs/Jetpack/Weekly Meeting/2010-10-05: Difference between revisions
< Labs | Jetpack | Weekly Meeting
Jump to navigation
Jump to search
m (→Minutes) |
No edit summary |
||
| Line 6: | Line 6: | ||
* Out-of-process Jetpack progress | * Out-of-process Jetpack progress | ||
** Atul completely ported the <code>request</code> module at [http://github.com/toolness/jetpack-e10s jetpack-e10s]. | ** Atul completely ported the <code>request</code> module at [http://github.com/toolness/jetpack-e10s jetpack-e10s]. | ||
* FlightDeck Updates - app, future development, new location on AMO wiki section | * [https://wiki.mozilla.org/AMO:Projects/FlightDeck FlightDeck Updates] - app, future development, new location on AMO wiki section [https://docs.google.com/document/edit?id=1q680sqwBaJ-0uz25tbi_osLJfi4UIBnBFtWAUVOHg2E&hl=en&authkey=CMjB_r4H# google doc] | ||
* roundtable | * roundtable | ||
** [http://toolness.github.com/reviewer-dashboard/ Atul's Jetpack reviewer dashboard] ([http://www.toolness.com/wp/?p=1081 blog post]) | ** [http://toolness.github.com/reviewer-dashboard/ Atul's Jetpack reviewer dashboard] ([http://www.toolness.com/wp/?p=1081 blog post]) | ||
Revision as of 21:23, 5 October 2010
Agenda
- followups from last meeting
- myk to solicit 0.9 plans from discussion group (thread)
- SDK 0.9 status
- Out-of-process Jetpack progress
- Atul completely ported the
requestmodule at jetpack-e10s.
- Atul completely ported the
- FlightDeck Updates - app, future development, new location on AMO wiki section google doc
- roundtable
- Atul's Jetpack reviewer dashboard (blog post)
- atul's github code review hack
- the general issue with object comparisons in the SDK
Minutes
- no response to Myk's solicitations-for-feedback about 0.9 plan. So it must be perfect! Freeze moved to 11am PDT Wednesday.
- Myk is working on making jetpack tests pass against FF nightly. Current best FF is b6, but warner saw test failures against current jetpack trunk.
- 0.9 status
- E10S integration: Atul ported Request, will work on the rest. Goal for 0.9 is to have an (unlanded) patch that provides framework that can get landed in subsequent release (0.10). Later releases have more pieces.
- identify dependencies by path (warner): should be ready for review tomorrow or thursday
- E10S-compatible Context Menu: Drew has patch waiting for review.
- use event-emitter model in high-level modules (irakli): some pieces are awaiting review, others still in development. Still on track.
- E10S-compatible Private Browsing: patches in review need updates.