Jetpack/Weekly Meeting/2014-02-11: Difference between revisions
Canuckistani (talk | contribs) (Created page with "__FORCETOC__ = Agenda = * High Priority Work ** [https://github.com/mozilla/addon-sdk/wiki/JEP-Add-on-debugger Add-on Debugger] ** [https://bugzilla.mozilla.org/show_bug.cgi?...") |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 12: | Line 12: | ||
** Blockers? | ** Blockers? | ||
* Roundtable | * Roundtable | ||
** Australis/UX update? | |||
= Bugs = | = Bugs = | ||
Line 31: | Line 32: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
= Attendees = | = Attendees = | ||
* zombie | |||
* Jordan | |||
* Irakli | |||
* Will | |||
* Erik | |||
* Jeff | |||
* Gabor | |||
* Matteo | |||
= Minutes = | = Minutes = | ||
== High Priority Work == | |||
===[https://github.com/mozilla/addon-sdk/wiki/JEP-Add-on-debugger Add-on Debugger]=== | |||
Add-on actor thread tests are done. They fail. | |||
===[https://bugzilla.mozilla.org/show_bug.cgi?id=915376 Native Jetpack Support]=== | |||
Landed l10n update, have a patch for simple-prefs. What's the bare minimum to ship JPM? What's the plan for shipping it? | |||
===[https://bugzilla.mozilla.org/show_bug.cgi?id=935109 node loader changes]=== | |||
We should take this off the high-priority list and track it with JPM. Let's review the high-priority list next week. | |||
===[Slaughterhouse] (needs public bug)=== | |||
Discuss strategy at work week. Gabor: switching on expanded principal for add-ons will break add-ons that expose objects to content (i.e. unsafeWindow.blah="foo" in a content script). Jeff: we can figure out which AMO add-ons will break here. | |||
===[https://github.com/mozilla/addon-sdk/pull/1353/files Devtools SDK]=== | |||
No update. | |||
===[https://bugzilla.mozilla.org/show_bug.cgi?id=961846 SDK 1.16]=== | |||
Have 1 issue still to resolve before we can ship. | |||
== Blockers == | |||
Erik needs Irakli to review something. | |||
== Roundtable == | |||
Aliases: Jordan wants to provide aliases for node modules: that is, to shim SDK modules so they expose node-like interfaces, so node applications can use them directly. We need to make sure add-ons that use aliased modules get appropriate review. Jeff: would like to not ship this in FF, not yet anyway: can we at least start by shipping it in NPM. | |||
UX modules in Firefox 29: Will would like to know what exactly is shipping in Firefox 29, so it can get documented. Will send out an email about it. |
Latest revision as of 01:30, 12 February 2014
Agenda
- High Priority Work
- Add-on Debugger
- Native Jetpack Support
- node loader changes
- [Slaughterhouse] (needs public bug)
- Devtools SDK
- SDK 1.16
- SDK
- Blockers?
- Roundtable
- Australis/UX update?
Bugs
Triage Followups
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Open Bugs
Bugzilla query error
Invalid type (count) and display (table) combination1
Attendees
- zombie
- Jordan
- Irakli
- Will
- Erik
- Jeff
- Gabor
- Matteo
Minutes
High Priority Work
Add-on Debugger
Add-on actor thread tests are done. They fail.
Native Jetpack Support
Landed l10n update, have a patch for simple-prefs. What's the bare minimum to ship JPM? What's the plan for shipping it?
node loader changes
We should take this off the high-priority list and track it with JPM. Let's review the high-priority list next week.
[Slaughterhouse] (needs public bug)
Discuss strategy at work week. Gabor: switching on expanded principal for add-ons will break add-ons that expose objects to content (i.e. unsafeWindow.blah="foo" in a content script). Jeff: we can figure out which AMO add-ons will break here.
Devtools SDK
No update.
SDK 1.16
Have 1 issue still to resolve before we can ship.
Blockers
Erik needs Irakli to review something.
Roundtable
Aliases: Jordan wants to provide aliases for node modules: that is, to shim SDK modules so they expose node-like interfaces, so node applications can use them directly. We need to make sure add-ons that use aliased modules get appropriate review. Jeff: would like to not ship this in FF, not yet anyway: can we at least start by shipping it in NPM.
UX modules in Firefox 29: Will would like to know what exactly is shipping in Firefox 29, so it can get documented. Will send out an email about it.