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: July 8, 2024 Next Release: July 9, 2024
Central: 129 Aurora: 54 Beta: 128 Release: 127
  • Beta 4
    • Desktop ships today
    • Mobile ships tomorrow
  • Next Beta release
    • Desktop Beta 5 gtb Thu, ships Fri
    • Mobile Beta 6 gtb Mon, ships Tue/Wed

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)

  • Seth Fowler has resolved a series of image-related memory usage regressions that have been present on AWSY since early November.

Stability (kairo)

<Read Only>

  • Overall numbers are still bad for everything other than desktop release (see beta/devedition bugs above, nightly crash rates are even worse).

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)

  • WebGL regression sadness on Windows related to ANGLE. Both in 32/33 (hardware/driver specific) and 35 (investigating.) Bugs 1122465 and 1123365.
  • Need to put tooling in place to see if it's shared memory that is soft-leaking, accounting for OOM on Windows.
  • Unified crashes due to driver resets, seeing crashreports at #4 which was before a long tail. Should help with tracking down the solutions.

JS (naveed)

<Read Only>

  • Compiler (JIT)
    • bug 1124002: Fix a bad performance issue with closure-compiled code (by removing some code).
    • bug 1125505: Posted patches to fix mutable __proto__ to not reshape the proto chain in common cases. This should make Shumway (raytrace.swf) a lot faster.

Layout (jet/dbaron)

Media (mreavy)

<Read Only>

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

  • bug 749703 from an external contributor broke WebRTC calls by exposing an existing bug/timing-hole (merged to m-c Saturday); a fix is about to land (bug 1126036)
    • Some end-to-end functional tests for Hello that are about to land would catch this; most in-single-browser tests as we have in mochitest suites can't/don't hit the timing issue introduced.

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

Necko (dougt/jduell)

Performance (vladan)

No update this week

Seceng (dougt)

Shumway (tschneidereit)

WebAPI (overholt)


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


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