Jetpack/Weekly Meeting/2012-09-25

From MozillaWiki
Jump to: navigation, search


Awesomeness Schedule

10/2 Will
10/9 Alex
10/16 Dave
10/23 Eddy
10/30 Erik
11/6 Gabor
11/13 Irakli
11/20 Jeff
11/27 Matteo


Triage Followups

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Open Bugs


  • Eddy
  • Gabor
  • Wes
  • Matteo
  • Irakli
  • Mossop
  • Jeff
  • Will
  • Erik
  • Alex



The Builder's not working. Jeff and Wes are investigating.


Q3 goals update

Q3 goals update. We will hit some Q3 goals, and miss others.

P1 goals:

  • improving mobile support done
  • repacks done, and email sent. Sent out 3-400 emails, we have 35 responses to the survey, and an uptick in add-on submissions to AMO (no hard numbers for that yet). We had a copule of problems with repacking old versions of add-ons, probably because the email took so long to send.
  • planning for landing in Firefox is done. Irakli will get feedback on this plan from Mossop. Jeff will talk about it in next week's dev planning meeting.
  • planning for UX is missed

P2 goals: some misses, some hits.

We've done other stuff too! Rewrote context-menu, added page-mod stuff.

Q4 goals

Mossop presented draft Q4 goals.

SDK 1.11 beta

Will go out today.


Awesomeness from Wes

blog post about releasing SDK 1.10. Great post because it made people realise how much of a nightmare it is for us.

Singapore plans

Talk to Jeff if you want to spread Jetpack goodness in Singapore: talks and workshops around add-ons, especially mobile.

Mozcamp talks from Eddy and Irakli.

Firefox schedule shift

Firefox is shifting its release schedule by a week so as not to ship on NYE 2012: We should do the same. Jeff will communicate it.

"The page-mod release"

Alex blogged about 1.11.

"1st Draft of integrating SDK into Firefox"

Irakli drafted the plan for landing in Firefox, and raised associated bugs.


Our indexed-db module, scheduled to land in 1.11 currently implements a workaround involving renaming databases. When we remove the workaround, will we break compatibility? Gabor: it will be hard not to break the API. If we know we are going to break the API soon, we should not release now, even as experimental. Removing the workaround depends on Firefox, so we probably can't do it for a few months, and we'd really like to ship indexed-db soon.

Let's raise a bug and take this discussion offline.