Jetpack/Weekly Meeting/2013-04-30

From MozillaWiki
Jump to: navigation, search


Agenda

  • High Priority Work
  • SDK
    • Blockers?
  • Roundtable
    • Should we ask for Aurora (or even Beta) uplift for bug 855651? We've apparently broken SDK addons for IceWeasel and company in SDK 1.14, and the fix for that won't hit an official Firefox release until sometime in August.
    • How/when should we resolve bugs now that we're shipping in Firefox?
      • When the fix lands in the github repository?
      • When we uplift that to inbound?
      • When that inbound uplift gets merged to m-c?
      • We have a github hook to auto-resolve when a commit message includes "fix bug xxxx", maybe we should disable or tweak it so it adds a whiteboard flag instead?
      • Can whatever system we choose be mostly automated (as part of m-cMerge, perhaps)?

Awesomeness Schedule

Awesome Date Awesome Person - Awesome thing
04/29 Eddy - Dutch Mozilla meetup
04/06 Erik - Content policies
05/13 Mossop - TBD
05/13  ???

Bugs

Triage Followups

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Open Bugs

Attendees

  • Irakli
  • Mossop
  • Wes
  • Gabor
  • Erik
  • DCamp
  • Will
  • Jordan

Minutes

High Priority Work

Cross-domain content scripts

Jordan will take over the SDK side of this. Gabor will advise.

UX Work

  • work on button almost complete
  • proposals for the other pieces are progressing
  • Erik: give us feedback on APIs

Places API

Jordan: please look at the proposed API and give us feedback.

DOM Window for add-ons

Irakli: this is still a work in progress.

The great last repack

Will: trying to figure out how we will be able to review ~1500 add-ons before Firefox 22 ships.

De-traitification

Irakli: no progress this week.

Blockers?

Erik: has a PR for chrome manifest support, with a permissions flag for authors to ask chrome.manifest to be included. Asking for feedback on whether this is the right thing to do.

Roundtable

Should we ask for Aurora (or even Beta) uplift for bug 855651?

We've apparently broken SDK addons for IceWeasel and company in SDK 1.14, and the fix for that won't hit an official Firefox release until sometime in August.

Mossop will ask for uplift today.

How/when should we resolve bugs now that we're shipping in Firefox?

  • When the fix lands in the github repository?
  • When we uplift that to inbound?
  • When that inbound uplift gets merged to m-c?
  • We have a github hook to auto-resolve when a commit message includes "fix bug xxxx", maybe we should disable or tweak it so it adds a whiteboard flag instead?
  • Can whatever system we choose be mostly automated (as part of m-cMerge, perhaps)?


We should stop marking our bugs fixed until they are uplifted to m-c, for consistency with the rest of Mozilla. Maybe GitHub hooks to add a whiteboard tag, then uplifts can mark tagged bugs as fixed? We need to work more on mechanics, but agreed that the principle is right.

Retrieved from "https://wiki.mozilla.org/index.php?title=Jetpack/Weekly_Meeting/2013-04-30&oldid=650951"