Labs/Jetpack/Weekly Meeting/2011-12-20: Difference between revisions

Line 27: Line 27:


= Minutes =
= Minutes =
=== Flightdeck ===
* sending email to gather AMO accounts for super users
* next release tomorrow
* keyboard shortcuts coming back next week
=== SDK ===
* 2011 Goals
** l10n
*** big discussion on 1st landing, negative comments
*** should press forward and land something
*** 'on track'
** mobile:
*** unit tests, written, create pull request, landing tomorrow?
** html localization
*** proposal being worked on, Thurs?
*** driving proposal unlikely to happen this year
*** 'risky'
** indexDB
*** new patch sent, hopefully landed this week
*** 'on track'
** addonTab
*** 'at risk'
*** underestimated work
*** implementation done, code needs to be reviewed
*** need strategy for code updated over multiple addons
**** details on bugzilla, pull requests
** unpacking xpis
*** 'at risk'
*** close, does all of the right stuff
*** needs review, fix some tests
* Question: table of version compatibility between firefox and SDK versions? Will can add it to the schedule table, should be easy to reference for users.
* Release process: Brian made some changes, Myk agrees. We now look at the git tag to set version, this affects the release process on the wiki: https://wiki.mozilla.org/Jetpack/Release_Process
=== Roundtable ===
* 2012 Roadmap
** initial sketch of goals & roadmap on the wiki
** shift of audience for the SDK, start targeting 'deep integrators', please review explanation in the roadmap: https://wiki.mozilla.org/Jetpack/Roadmap and Goals: https://wiki.mozilla.org/Jetpack/Goals/2012-Goals
* Comment from Will: 3rd party modules on the roadmap? Not included yet, but in the goals for Q4.
* no metrics yet, suggestions welcome?
** AMO fast track review queue as a metric
* simplify reviews of addons that use common modules
* AMO-validator data is updated?
** Jeff: will follow-up with AMO on validator updates
* Use of P4 priorities
** personal / work item bugs, given P4 stats in triage.
** engineers should be managing them
** putting these bugs means 'not subject to triage any more', engineers should challenge P4 status when appropriate
** makes sense to prioritize your own bugs P4 if they fall into this bucket
* Github access controls, prevent people from committing?
** possible in future
** various techniques to prevent unwanted pushes
*Extra eyes on stabilization branch?
** make sure it looks okay after the last few days
* Ownership of builder helper add-on
** needs refactoring?
** newer features in Fx could simplify codebase
** who owns this?
** Alex will take a look
* cfx upload / cfx source-package
* upload source package to AMO
* helps repacker, possibly Flight deck
* will help l10n as well, to have non-packed version
* devtools team is looking at source mapping?
* various workflow options could be opened up, e.g. commit to github refreshes source package on AMO
* Myk is spinning 1.4b3 today, anything that needs to get into this, ping him.
* Matteo: Fennec patch landed tomorrow, goes in 1.4?
* Myk: no, 1.5.
* Jeff: how to test?
* Myk: we need docs
* Matteo: will do.
Confirmed users
1,100

edits