Platform/2015-01-06

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 (lsblakk/sylvestre/lmandel)

Next Merge: January 6, 2020 Next Release: January 7, 2020
Trains
Central: 73 Aurora: 54 Beta: 72 Release: 71.0
  • 35.0 Desktop RC builds with QA
  • 35.0b10 mobile - need to figure out what's happening with bug 1073554
  • 31.4.esr builds with QA
  • Next week we'll be doing a throttling change where the plan (unless there are known issues in the wild) will be to enable updates at 100% on Friday Jan 16th (4 days earlier than current)


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>


DMD is now working reliably on Mac, and also seems to be working on Fennec. Follow the instructions and try it out!


Stability (kairo)

  • bug 1088148 is a supposed a11y crash fix that triggered a huge spike in its own crash signature. This is 1/3 of current Nightly crashes!
  • bug 1116825 was a significant plugin crash spike, but fix should just have landed.

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)

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

  • bug 1110215: Disabled Flash protected mode on Beta as an experiment. See bug 1111791 for a report on the results.

Q1 plans: [1]

  • Video/Flash fixup
  • e10s
  • telemetry/FHR unification
  • update orphaning
  • catastrophic memory usage


Developer Services (gps/lthomson)

Developer Tools (prouget)

DOM (jst/overholt)

Electrolysis (e10s) (blassey)

  • e10s will be disabled (bug 1117867) for this last week of Nightly 37 to shake out any non-e10s bugs.
  • e10s will be reenabled (bug 1117934) next week for Nightly 38 testing.


Firefox Desktop (gavin)

Firefox Mobile (snorp/blassey/mfinkle)

GFX (milan)

<Read Only>

  • Most of the team is back online this week. Catching up.
  • Items for 37-B2G-Aurora landings are on track.

JS (naveed)

Layout (jet/dbaron)

<Read Only>

For Q1 priorities, see the "Current Plans" section here:

Media (mreavy)

<Read Only>

0. What are your team's plans for Q1 that might impact others?

  • Multistream and renegotiation support for WebRTC
  • Hello front-end development transitioning from Platform to Firefox

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

  • Second phase of Hello/Loop about to hit release/35 (Rooms redesign)

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

  • Expecting to land major webrtc upstream code update immediately after 37 uplifts
    • Already green on Win/Mac/Linux


Necko (dougt/jduell)

Performance (vladan)

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

a) bug 998863: Asynchronous initialization of plugins has landed

  • It's currently preffed *OFF* by default, please help us test it: set dom.ipc.plugins.asyncInit to true
    • There are stability problems with e10s at the moment, Aaron is working on fixing these issues
    • Mark any bug reports as blockers of bug 1116806

b) Many Telemetry measurements are biased by users who submit many short sessions (vs users with fewer, longer sessions). You can remove this bias by doing your analysis "per user" using the new clientID field:

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

  • bug 1021842: A-Team and Perf team are working on making the Talos regression detection formula more accurate
  • We're going to try to have devs make a decision (wontfix, will fix before branch date, etc) on each Talos regression within 2 weeks of the regression bug being filed


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