Platform/2013-11-05

From MozillaWiki
Jump to navigation Jump to search


« previous week | index | next week »

Engineering Meeting Details

  • Tuesday 2013-11-05 - 11:00 am Pacific
  • 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 Warp Core / TOR Finch / SFO Warfield / PDX Widmer
  • join irc.mozilla.org #planning for back channel

Actions

Hot Bugs

(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)

Orange Factor
Stability
Other

The Need To Know

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

Notices/Schedule (akeybl/lsblakk/bajaj)

Next Merge: July 8, 2024 Next Release: July 9, 2024
Trains
Central: 129 Aurora: 54 Beta: 128 Release: 127
?? bugs (?? bugs last week)
?? bugs (?? bugs last week)
Unresolved Aurora 54 Trackers (non-security, not tracked for Beta) Unresolved Beta 128 Trackers (non-security)

Build Changes (gps)

(Build changes of which engineers should be aware.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Key Issues

(Non team specific issues that impact engineering.)

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

Accessibility (dbolter)

  • New bugzilla flag! "a11y-review"
    • Definition/Usage: This flag is used to ask the accessibility team to look over a bug. Typically used if a bug has the potential to affect accessibility, regresses accessibility, and/or is a new user facing feature.
    • Currently available for these products: Firefox, Firefox for Android, Core, Toolkit, Firefox OS.
    • We're here to help.

Add-on SDK (dtownsend)

App Tools (dtownsend)

B2G Services (dougt)

  • Blog posted on stumbling. Created 4 new developers, lots of interest.

Developer Tools (robcee)

DOM (jst/dougt)

Firefox Desktop (gavin)

Firefox Metro (bbondy/jmathies/mbrubeck)

Firefox Mobile (mfinkle/blassey)

Firefox OS Communications (scravag)

Firefox OS Devices/Porting (mchen)

Firefox OS Media Apps (hema)

Firefox OS Media Recording (cjku)

Firefox OS Performance (mlee)

Firefox OS Productivity (doliver)

Firefox OS Radio/Bluetooth/GPS (kenhkchang)

Firefox OS Systems - Front End (gwagner)

Firefox OS Systems - Platform (timdream)

GFX (milan)

Identity (jedp)

JS (naveed)

Layout (jet/dbaron)

Media (mreavy)

<Read Only>

  • IETF conference is this week, W3 conference is the week after. Several WebRTC team members are at these.
  • Update to webrtc.org code (moving to version 3.43) will probably land this week. If you have questions, please contact Randell Jesup.
  • If you haven't seen it already, check out: https://brendaneich.com/2013/10/ciscos-h-264-good-news/

Necko (dougt/jduell)

Performance (vladan)

Seceng (mmc)

WebAPI (overholt)

Quality Programs

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

CritSmash (dbolter)

MemShrink (njn)

The trees were closed for several days due to shutdown leaks. From the post-mortem:

TL;DR: Win7 M2 and Mbc test were OOMing frequently at shutdown because too many DOM windows were open. This was due to a combination of: (a) multiple badly written tests, (b) multiple social API leaks, (c) multiple devtool leaks. Bug 932898 will improve our shutdown leak detection; bug 934288 may also help. Bug 932900 will (if implemented) will make some of these leaks impossible(?).

OrangeFactor (ryanvm)

Stability (kairo/bsmedberg)

Roundtable

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

<Read only beyond this point>

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