Labs/Jetpack/Weekly Meeting/2010-06-22

Agenda

• followups from last week
• SDK 0.5 status
• FlightDeck 1.0a2 status
• Q3 project goals
• SDK 0.6 planning
• startup events
• roundtable
  • what makes the SDK 1.0? (see below)

Minutes

• SDK 0.5 status
  • three RCs, last one spun yesterday. No respin-inducing bugs appeared so far. Needs at least one more day to bake. Likely to release on thursday (to align with FlightDeck release).

• FlightDeck status
  • tenatively froze last tuesday, tutorial landed saturday
  • Myk found some blockers in casual testing, feels fragile
  • if last blocker is fixed today, we could bake for two days and still ship on thursday. Feels dubious though.
  • Please Test!! Talk to dbuc for access.

• Q3 goals
  • general goal is 1.0 in Q4, not specifically aligned to fx4
  • which probably means feature-complete beta in Q3
  • potential goals:
    • feedback channel
    • exit incubation: move servers out of labs onto AMO hardware, process stuff
    • collaborative development feature
    • project branch for unit tests (if slips Q2)
    • integration testing
    • performance testing
    • security model in place
    • packaging minimization (don't package unused modules)
    • better debugging tools
    • module repository (ala node.js)

1.0

What makes the SDK feature-complete for 1.0? Some ideas below. What's missing? How can we get feedback on this from addon developers, both old-school and those using the SDK?

• Chrome privilege separation
• E10s conversion of APIs
• Panels
• Page-mods
• Places
• Windows
• Sidebar
• Preferences (myk clarify?)
• Database (sqlite)
• Clipboard
• Keyboard
• Menus