Jetpack/Weekly Meeting/2012-2-14: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Agenda =
= Agenda =


* Wes!
* Flightdeck
* Flightdeck
* SDK
* SDK
** Cherrypicking 724433 to stabilization for 1.5RC2
** Cherrypicking 724433 to stabilization for 1.5RC2
** Anything else for RC2?
** Anything else for RC2?
** Uh-oh: https://bugzilla.mozilla.org/show_bug.cgi?id=726967
*** Whimboo says this could be bad for repacks?
* Roundtable
* Roundtable


= Pending Requests=
= Pending Requests=
* Bugs with pending requests
* http://kwierso.github.com/Jetpack-Bugzilla-Organizer/requests/
* http://kwierso.github.com/Jetpack-Bugzilla-Organizer/requests/
 
* Bugs with pending requests as of midnight:
** Bug 704357
*** Irakli asking Alex to review
** Bug 723584
*** Will asking review from warner and feedback from dcm
*** If this can get reviewed and landed today, it can be cherrypicked for 1.5
** Bug 723555
*** Irakli asking Alex to review


= Attendees =
= Attendees =


= Minutes =
= Minutes =
* Wes became a Mozilla employee. Applause!


=== Flightdeck ===
=== Flightdeck ===
* bug 724766 (500 error when accessing dashboard)is still blocking 1.0. We have a patch in testing.
* will have the video reshot for Wednesday
* SDK 1.5 will require a repack, preparing to test that.


=== SDK ===
=== SDK ===
* release 1.5 next week
* will require a repack: must make sure add-on developers know about this.
* RC2 today: cherrypick 724433, plus a couple of documentation bugs
** (new) serious bug found: 726967. It appears to be introduced in Firefox 12 and 13: so may be OK to leave out of 1.5
** ochameau: about to push a memory leak fix, will be useful to have in 1.5
* gozala: tinderbox is reporting an error on Firefox nightly builds. we should have a bug for this


=== Roundtable ===
=== Roundtable ===
* dietrich gave an update on the project to deliver new Firefox features as add-ons. Recent discussions focused on which of these should land in Firefox and which should stay add-ons. Some use the SDK heavily, some only use it as a loader. It's instructive to see the different ways people can use Jetpack. Why do some add-ons work better with Jetpack than others? Understanding this will help the SDK team make the SDK more suitable for heavy-duty add-on development. Dietrich welcomes the Jetpack team to attend the meetings!
* Share is planning to land in moz-central
* pdf.js, browserid, are up in the air at the moment
* also talking about getting the SDK itself landed into the Firefox (possibly as an add-on itself?) Drew Willcoxon wrote up a proposal for this, which you can read here: https://etherpad.mozilla.org/jetpack-in-firefox-estimate

Latest revision as of 00:14, 15 February 2012

Agenda

Pending Requests

  • http://kwierso.github.com/Jetpack-Bugzilla-Organizer/requests/
  • Bugs with pending requests as of midnight:
    • Bug 704357
      • Irakli asking Alex to review
    • Bug 723584
      • Will asking review from warner and feedback from dcm
      • If this can get reviewed and landed today, it can be cherrypicked for 1.5
    • Bug 723555
      • Irakli asking Alex to review

Attendees

Minutes

  • Wes became a Mozilla employee. Applause!

Flightdeck

  • bug 724766 (500 error when accessing dashboard)is still blocking 1.0. We have a patch in testing.
  • will have the video reshot for Wednesday
  • SDK 1.5 will require a repack, preparing to test that.

SDK

  • release 1.5 next week
  • will require a repack: must make sure add-on developers know about this.
  • RC2 today: cherrypick 724433, plus a couple of documentation bugs
    • (new) serious bug found: 726967. It appears to be introduced in Firefox 12 and 13: so may be OK to leave out of 1.5
    • ochameau: about to push a memory leak fix, will be useful to have in 1.5
  • gozala: tinderbox is reporting an error on Firefox nightly builds. we should have a bug for this

Roundtable

  • dietrich gave an update on the project to deliver new Firefox features as add-ons. Recent discussions focused on which of these should land in Firefox and which should stay add-ons. Some use the SDK heavily, some only use it as a loader. It's instructive to see the different ways people can use Jetpack. Why do some add-ons work better with Jetpack than others? Understanding this will help the SDK team make the SDK more suitable for heavy-duty add-on development. Dietrich welcomes the Jetpack team to attend the meetings!
  • Share is planning to land in moz-central
  • pdf.js, browserid, are up in the air at the moment
  • also talking about getting the SDK itself landed into the Firefox (possibly as an add-on itself?) Drew Willcoxon wrote up a proposal for this, which you can read here: https://etherpad.mozilla.org/jetpack-in-firefox-estimate