Jetpack/Weekly Meeting/2012-07-17: Difference between revisions
< Jetpack | Weekly Meeting
Jump to navigation
Jump to search
(→Agenda) |
Canuckistani (talk | contribs) (→SDK) |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 8: | Line 8: | ||
** Anything for 1.9b2 that isn't in 1.9b1? Tell Wes soon, or you'll miss the beta! | ** Anything for 1.9b2 that isn't in 1.9b1? Tell Wes soon, or you'll miss the beta! | ||
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=774636 bug 774636] Deprecate Components with message before removing it | *** [https://bugzilla.mozilla.org/show_bug.cgi?id=774636 bug 774636] Deprecate Components with message before removing it | ||
*** [https://github.com/mozilla/addon-sdk/pull/466 pull 466] Updated runner.js with a better observer's topic for Fennec | |||
** Changes coming to private browsing {{bug|748604}} - needs an owner | ** Changes coming to private browsing {{bug|748604}} - needs an owner | ||
* Roundtable | * Roundtable | ||
Line 14: | Line 15: | ||
** Wes is working on a new bug dashboard: http://kwierso.github.com/Jetpack-Bugzilla-Organizer/newrewrite/ (Feedback welcome!) | ** Wes is working on a new bug dashboard: http://kwierso.github.com/Jetpack-Bugzilla-Organizer/newrewrite/ (Feedback welcome!) | ||
** Would be really cool to use `Target milestone` field in bugzilla when we land the related fix. (And ensure always filling bugs for errors/exception that users can face.) | ** Would be really cool to use `Target milestone` field in bugzilla when we land the related fix. (And ensure always filling bugs for errors/exception that users can face.) | ||
** Nigthly support and AMO. Needs to wait for final 1.9 (?) to upload a fix for nightly support. | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683217 bug 683217] ( " {Cu} = require("chrome"); doesn't let you use Cu.import("somejsmodule");" ) has reared its ugly head. | |||
= Bugs = | = Bugs = | ||
Line 34: | Line 37: | ||
</bugzilla> | </bugzilla> | ||
= Attendees = | = Attendees = | ||
* Gabor | |||
* Jeff Griffiths | |||
* Wes | |||
* Eddy | |||
* Irakli | |||
* Jeff Hammel | |||
* Erik | |||
* Matteo | |||
* Mossop | |||
* Alex | |||
* Will | |||
= Minutes = | = Minutes = | ||
=== Builder === | === Builder === | ||
* sent email to builder team to make sure they still exist | |||
* 1.8.1 still not up yet - Jeff will talk will clouser | |||
=== SDK === | === SDK === | ||
* Q3 goals: https://wiki.mozilla.org/Jetpack/Goals/2012Q3 | |||
** mobile is the focus | |||
** Will: 3rd party modules? Will will look into this. | |||
* UX progress | |||
** lots of work to do | |||
** use mercurial to produce try builds? | |||
* anything for 1.9 beta? | |||
** Matteo - mobile fix | |||
** Irakli - panel is broken on nightly. fixed? 774088 | |||
* private Browsing API changes | |||
** erik took the bug | |||
** change to how pb module works, need stats on usage of the old module? | |||
** outreach to 24 users of the module? | |||
=== Roundtable === | === Roundtable === | ||
* re-packs are good, high confidence! | |||
** also have ftp access | |||
** can re-pack to 1.8.1 | |||
* nightly support? | |||
** look at releaseing beta / rc signature updates | |||
** jeff to talk to will clouser about weekly releases | |||
** potential first candidate is today's beta. | |||
* we should use target milestone field in bugzilla - easier tracking of bug <==> release! | |||
* Cu.import behaviour differs in SDK | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683217 bug 683217] reveals this is actually unintended behaviour | |||
** traditional platform devs expext `import *` behaviour, but current behaviour is preferred as it does not blindly pollute the scope. | |||
** options: document current behaviour, implement expected behaviour, implement something else? |
Latest revision as of 23:01, 17 July 2012
Agenda
- Builder
- SDK
- Q3 Goals
- UX progress?
- Anything for 1.9b2 that isn't in 1.9b1? Tell Wes soon, or you'll miss the beta!
- bug 774636 Deprecate Components with message before removing it
- pull 466 Updated runner.js with a better observer's topic for Fennec
- Changes coming to private browsing bug 748604 - needs an owner
- Roundtable
- re-pack progress: ready to go, need to confirm repacking against 1.8.1
- Jeff -> Brazil
- Wes is working on a new bug dashboard: http://kwierso.github.com/Jetpack-Bugzilla-Organizer/newrewrite/ (Feedback welcome!)
- Would be really cool to use `Target milestone` field in bugzilla when we land the related fix. (And ensure always filling bugs for errors/exception that users can face.)
- Nigthly support and AMO. Needs to wait for final 1.9 (?) to upload a fix for nightly support.
- bug 683217 ( " {Cu} = require("chrome"); doesn't let you use Cu.import("somejsmodule");" ) has reared its ugly head.
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
- Gabor
- Jeff Griffiths
- Wes
- Eddy
- Irakli
- Jeff Hammel
- Erik
- Matteo
- Mossop
- Alex
- Will
Minutes
Builder
- sent email to builder team to make sure they still exist
- 1.8.1 still not up yet - Jeff will talk will clouser
SDK
- Q3 goals: https://wiki.mozilla.org/Jetpack/Goals/2012Q3
- mobile is the focus
- Will: 3rd party modules? Will will look into this.
- UX progress
- lots of work to do
- use mercurial to produce try builds?
- anything for 1.9 beta?
- Matteo - mobile fix
- Irakli - panel is broken on nightly. fixed? 774088
- private Browsing API changes
- erik took the bug
- change to how pb module works, need stats on usage of the old module?
- outreach to 24 users of the module?
Roundtable
- re-packs are good, high confidence!
- also have ftp access
- can re-pack to 1.8.1
- nightly support?
- look at releaseing beta / rc signature updates
- jeff to talk to will clouser about weekly releases
- potential first candidate is today's beta.
- we should use target milestone field in bugzilla - easier tracking of bug <==> release!
- Cu.import behaviour differs in SDK
- bug 683217 reveals this is actually unintended behaviour
- traditional platform devs expext `import *` behaviour, but current behaviour is preferred as it does not blindly pollute the scope.
- options: document current behaviour, implement expected behaviour, implement something else?