Platform/2014-10-28

« previous week | index | next week »

Engineering Meeting Details

• Tuesday 2014-10-28 - 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 irc.mozilla.org #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
Trains
Central: 129	Aurora: 54	Beta: 128	Release: 127

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

• Tree Closing Window on Saturday, November 1. bug 1087431 is the tracker.
  • An unusually long window -- approx 11-1/2 hours.
  • Most of the work is network related, with interruptions in traffic from time to time.
  • We'll leave trees "open", but developers should expect longer than normal build times and potential need to restart some jobs.

Quality Programs

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

MemShrink (njn)

• Valentin Gosu fixed a significant memory regression involving resource timing that was detected by AWSY.
• Mike Hommey landed logalloc, a tool for recording and replaying heap allocations. It will allow easier testing of different heap allocators, such as jemalloc3.

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

Electrolysis (e10s) (blassey)

• Please help dogfood e10s in Nightly!
  • To opt-in, open "Preferences" and check the "Enable E10S (multi-process)" checkbox.
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

• Enabling more e10s tests
• Watch for add-on breakage even with e10s disabled from bug 1030420 ("Enable dom.compartment_per_addon by default on Nightly"). This change is intended to help find e10s add-on bugs, even when e10s is disabled.

• Big changes to e10s printing (bug 927188) and plugins (bug 641685, bug 669200, bug 1044182) coming soon
• e10s maybe be enabled by default for Nightly testing within the next couple weeks, so please your test features and favorite add-ons now!
  • Add-ons that specifically marked as e10s-compatible in their manifests will be disabled (bug 1088309) on e10s first run, but brave testers can reenable them.

Roundtable

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

• Portland All-Hands
  • (Milan) Would like to have a session in Portland on alternatives to crash reports to get us back "bad failures". For example, we detect a bad driver, which leads to a the sub-optimal experience for the user. We fall back to non-accelerated setup, and warn the user about it, also letting them send us the information similar to what crash report would send. We'd need a lot of different teams represented - who should come, who should run with this?
  • Portland All-Hands free time blocks wiki to advertise BoF sessions.

<Read only beyond this point>

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