Jetpack/Weekly Meeting/2012-10-16: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 13: Line 13:
** Context-menu work is [https://github.com/mozilla/addon-sdk/pull/599 up for feedback], some minor API changes.
** Context-menu work is [https://github.com/mozilla/addon-sdk/pull/599 up for feedback], some minor API changes.
** Gregg Lind from UX Research wants to show off mods to Esprima, Escodegen, and CoverJS that should make it possible to do code coverage.  (he has to be done by 10:30 though for his own team meeting!)  [https://bugzilla.mozilla.org/show_bug.cgi?id=789401 bug 789401]  [https://gist.github.com/3900355 coverage recipe]
** Gregg Lind from UX Research wants to show off mods to Esprima, Escodegen, and CoverJS that should make it possible to do code coverage.  (he has to be done by 10:30 though for his own team meeting!)  [https://bugzilla.mozilla.org/show_bug.cgi?id=789401 bug 789401]  [https://gist.github.com/3900355 coverage recipe]
** [https://docs.google.com/spreadsheet/ccc?key=0ApEBy-GRnGxzdHlRMHJ5RXN1aWJ4RGhINkxSd0FCQXc#gid=0 Data about API usage by addons]
** Let's disable fennec test that fail on fennec so cfx testall is happy.
** Interrogation tests for fennec.


=Awesomeness Schedule=
=Awesomeness Schedule=

Revision as of 17:14, 16 October 2012


Agenda

  • Builder
    • all quiet on the western front
  • SDK
    • releasing 1.11rc1 with some hotfixes to cover deprecation of private-browsing features.
      • Anything else need to get in for this first RC build? If we can get it finalized soon, it'll help with shipping it in a few weeks.
    • investigating an auto-re-pack of simple add-ons to 1.11 shortly following release ( may need to wait until 1.12 if there are AMO issues )
    • Stumbling through the code, I found this comment about removing a chunk of code sometime after 1.0b5's release, when all frontends like Flightdeck have been updated to not use it. Are we there yet?
  • Roundtable
    • I (Wes) just hid the Jetpack tests run against Firefox Beta on OS X Leopard because those builds don't exist as of last Tuesday. That leaves just Release Firefox visible, but the tests are still being run on all four branches because that's how the test infrastructure works. Is it still worth the computing power consumed by attempting to run these tests when we only only see 1/4 of the results? Can we just stop running them entirely? When should we go ahead with bug 778969?
    • Context-menu work is up for feedback, some minor API changes.
    • Gregg Lind from UX Research wants to show off mods to Esprima, Escodegen, and CoverJS that should make it possible to do code coverage. (he has to be done by 10:30 though for his own team meeting!) bug 789401 coverage recipe
    • Data about API usage by addons
    • Let's disable fennec test that fail on fennec so cfx testall is happy.
    • Interrogation tests for fennec.

Awesomeness Schedule

10/23 Eddy
10/30 Erik
11/6 Gabor
11/13 Irakli
11/20 Jeff
11/27 Matteo
12/4 Wes
12/7 Will
12/14 Alex
12/21 Dave

Bugs

Triage Followups

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Open Bugs

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Attendees

Minutes

Builder

SDK

Roundtable

Retrieved from "https://wiki.mozilla.org/index.php?title=Jetpack/Weekly_Meeting/2012-10-16&oldid=480400"