Meeting Notes Meetings notes from the Mozilla community

Need To Know

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

Notices/Schedule (lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

• Desktop 36 Beta 7
  • shipped on Saturday – thanks to the teams that helped ship on the weekend
  • disabled MSE
  • did not ship on Windows because we were waiting for a fix for YouTube
  • we will likely ship a Desktop Beta 10 as a result

• Desktop and Mobile Beta 8 should ship today

• Reminder that the next merge is < 2 weeks away. 38 is the next major Firefox release and the next ESR release. Get yer fixes in!

• Aurora 37 is still not in good shape stability wise

• ekyle has created a page that shows Firefox tracked bugs per dev team for Beta and Aurora. This will be going up on the in office screens soon. Check it out. http://people.mozilla.org/~klahnakoski/platform/releases.html

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.)

MemShrink (njn)

<Read Only>

PLDHashTable (and nsTHashtable and friends) now do not allocate any entry storage until the first element has been added. This makes empty tables more space-efficient and there’s no longer any need to lazily initialize such tables.

Stability (kairo)

<Read Only>

• Overall numbers are still bad for everything else than release.
  • With 35.0.1 released, Firefox for Android looks fine on release now.
  • Desktop Beta should improve with MSE disabled in today’s beta. D2D 1.1 will also be disabled before we ship 36. We’ll try again next cycle.
  • Developer Edition sees a real lot of graphics crashes, we’ll need to see that cleaned up, hopefully a big part of that before we go to beta.

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.)

Desktop Platform (bsmedberg)

• Reminder: FHR and telemetry are being unified, hopefully for 38 cycle. All new measurements should be added to telemetry, no matter whether you want them for only prerelease or release populations.

Electrolysis (e10s) (blassey)

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

GFX (milan)

<Read Only>

• Planned “final” push for Lollipop, Silk in progress. More so for Silk than Lollipop, there are things outside our hands for Android L.
• Chasing down those Windows OOMs.
• Still a few unresolved Windows 7 issues on Beta 36.

Media (mreavy)

<Read Only>

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

• OpenH264 v1.3 now being pushed to release-channel users

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

• Fixing some OpenH264 vs WebRTC 40 update issues (packetization)
• Working on some regressions for getUserMedia (camera access) on specific Android devices
• Loop/Hello will be updating the server and unthrottling soon
• Preparing to land webrtc renegotiation (windows timer limits, etc)

Performance (vladan)

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

1. You can now do custom Telemetry analyses using a Spark cluster consisting of multiple nodes! Analyses of large volumes of data should be significantly faster.

• Launch a cluster from https://telemetry-dash.mozilla.org/
• Instructions: http://robertovitillo.com/2015/01/16/next-gen-data-analysis-framework-for-telemetry/
• You will soon be able to use Spark for Telemetry cron-jobs as well

2. FHR & Telemetry are being unified and some of the patches have caused a couple of Telemetry outages on Nightly 38. Make sure to check for expected # of submissions when looking at Telemetry dashboards or doing a custom Telemetry analysis.
3. David Teller (Yoric) has been on sick leave for the last few weeks

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

• bug 1128768: Develop a mechanism for reporting on the behavior of categories of Flash content (e.g. Facebook video, banner ads, YouTube player, etc) in a privacy-sensitive way. No URLs or domains are ever collected
  • This will be used to evaluate performance benefits of switching certain types of Flash content to Shumway

Roundtable

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

• All extensions will soon need to be signed – announcement: http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/

Links

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.)

• Google plans to remove Chrome support for SPDY in early 2016: Hello HTTP/2, Goodbye SPDY
• Microsoft already removed IE support for SPDY in Windows 10 Technical Preview: https://twitter.com/jacobrossi/status/564877789145214976

irc #planning Log From This Meeting

---