Platform/2013-06-18

« previous week | index | next week »

Engineering Meeting Details

• Tuesday 2013-06-18 - 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 / Warp Core / SFO-Boardroom / Tor Commons
• join irc.mozilla.org #planning for back channel

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)

?? bugs (?? bugs last week)	?? bugs (?? bugs last week)
Unresolved Aurora 54 Trackers (non-security, not tracked for Beta)	Unresolved Beta 128 Trackers (non-security)

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

Firefox Metro (bbondy/jmathies/mbrubeck)

<Read Only>

• team status updates
• Continued work on front end polish
• improvements to chrome input selection
• progress being made on getting dev tools/profiler hooked up. (bug 850019)
• Currently hooking up Async Pan Zoom Controller to Metro in (bug 849266 and bug 801154), Desktop Wiin32 to follow

GFX (milan)

<Read Only>

• See previous week

Media (mreavy)

<Read Only>

• Web Audio work is mostly done, only a few bits of the API remain to be implemented.
• Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.
• Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!
• Created WebVTT wiki page for status and getting-started links.
• This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.

Quality Programs

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

Memshrink (njn)

A big week.

• Brian Hackett enabled lazy bytecode. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which is practice is ~50% of them due to extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.

• Nils Maier implemented separate measurement of add-on compartments in about:memory. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.

• The report on MemShrink's 2nd birthday includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.

• MemShrink progress report, week 103-104. Future progress reports will now be every four weeks, rather than every two weeks.

Roundtable

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

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