From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Engineering Meeting Details

  • Tuesday 2014-12-09 - 11:00 am Pacific Standard Time
  • Dial-in: Audio-only conference# 98411
    • People with Mozilla phones or softphones please dial x4000 Conf# 98411
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 98411
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 98411
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 98411
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 98411
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 98411
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 98411
    • UK/London: +44 (0)207 855 3000, x4000 Conf# 98411
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 98411
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number
  • Engineering Vidyo Room / Air Mozilla / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
  • join #planning for back channel

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lsblakk/sylvestre/lmandel)

Next Merge: July 8, 2024 Next Release: July 9, 2024
Central: 129 Aurora: 54 Beta: 128 Release: 127
  • Firefox 34.0.5 updates are enabled at 100% as of this morning
  • We might need to do a mobile-only 34.0.1
  • Firefox Beta 35.0b2 shipping today
  • Fennec Beta 35.0b2 delayed go to build until Thursday
    • We're still working on split apk for Gingerbread users, should have that in place in the next couple of weeks

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

OrangeFactor (ryanvm)

CritSmash (dbolter)

MemShrink (njn)

<Read Only> No update.

Stability (kairo)

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

A*Team (jgriffin)

Accessibility (dbolter)

B2G Services (dougt)

Cloud Services (mmayo)

Desktop Platform (bsmedberg)

Developer Services (gps/lthomson)

Developer Tools (prouget)

DOM (jst/overholt)

Electrolysis (e10s) (blassey)

Firefox Desktop (gavin)

Firefox Mobile (snorp/blassey/mfinkle)

GFX (milan)

  • B2G: the follow up to 2.1 ("2.X") looks to be based on Gecko 37...
    • Graphics plans are unchanged from 2.2 to 2.X
    • Graphics plans were based on Gecko 38
    • So... will likely keep the 38 time frame and uplift to B2G 37 branch past the trunk. Will figure it out by mid January when this becomes relevant.

JS (naveed)

  • Work Week
    • Shumway load time is highest priority
    • 2015 Planning (more on this to come)

Layout (jet/dbaron)

<Read Only>

  • Investigating bug 1107378 to fix webkit-dependent sites in China added to a mobile (fennec) fix-list.
  • Landed bug 1089417 - restyling fixes for CSS media queries

Media (mreavy)

<Read Only>

  • 1. What has your team done since last week that might impact others?
    • Hello is in Release/34! Early reviews are generally good (and recognize the differences for privacy compared to say Skype).
    • Landed sdparta! bug 1091242 - (rewrite of the majority of webrtc signaling, other than the parsing).
      • Known regression bug 1109130 breaks < MSVC 2013 compiles; fix shortly
    • Lots of great discussions at #mozlandia
    • FoxEye presentation (echoes of roc's older MediaStream Processing proposal)
    • Work moving forward towards multiple streams of a type and renegotiation
  • 2. What will your team do this week that might impact others?
    • Starting work towards a update
    • More sdparta work

Necko (dougt/jduell)

Performance (vladan)

1. What has your team done since last week that might impact others?

  • bug 1107779, bug 1107782: Avi found that the "activeTicks" FHR measurement significantly over-reports Firefox usage time, because Firefox fires "user-interaction-active" notifications while the mouse cursor is positioned over the browser even when the user is away from the computer
    • Should we just land the fix, or is it important to maintain continuity with the current measurement (for monitoring for relative changes)?
    • The above bugs are unrelated to the big drop in activeTicks reported in bug 1096498
  • Talos numbers for most E10s tests are available
    • we're still converting some tests, e.g. tresize
    • there are serious regressions from E10S, e.g. WebGL is 4x worse on Windows
    • Joel Maher said he'll write a blog post summarizing Talos regressions/improvements from E10S
  • Spark is the new, much faster way of analyzing large amounts of Telemetry data:

2. What will your team do this week that might impact others?

  • bug 998863: Almost ready to land asynchronous initialization of out-of-process plugins

3. Is anything slowing your team down or getting in their way?

  • bug 998863: Need one more review for asynchronous initialization of out-of-process plugins

Seceng (dougt)

Shumway (tschneidereit)

WebAPI (overholt)


(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Touch input standardization update (mbrubeck)

  • W3C Pointer Events going to Proposed Rec. Shipping in IE, portions shipping in Chrome, partially implemented in Gecko.
    • Chrome and Safari have no plans to ship full Pointer Events implementation.
  • Touch Events CG is actively discussing errata and extensions, about to start a weekly-ish telecon. Let me know if you want to get involved.
  • Gecko/Touch has a breakdown of our implementation status and various missing pieces.


Friends of the Tree

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting