Platform/2015-02-10

From MozillaWiki
Jump to: navigation, search


« previous week | index | next week »

Engineering Meeting Details

  • 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

Need To Know

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

Notices/Schedule (lmandel)

Next Merge: September 2, 2019 Next Release: September 3, 2019
Trains
Central: 70 Aurora: 54 Beta: 69 Release: 68.0
  • 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

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>

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

A*Team (jgriffin)

Accessibility (dbolter)

B2G Services (dougt)

Cloud Services (mmayo)

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.

Developer Services (gps/lthomson)

Developer Tools (prouget)

DOM (jst/overholt)

Electrolysis (e10s) (blassey)

Firefox Desktop (gavin)

Firefox Mobile (snorp/blassey/mfinkle)

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.

JS (naveed)

Layout (jet/dbaron)

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)


Necko (dougt/jduell)

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.

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


Seceng (dougt)

Shumway (tschneidereit)

WebAPI (overholt)

Roundtable

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

Links

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