Meeting Notes Meetings notes from the Mozilla community

19-July-2011

Mozilla Platform Meeting Minutes: 2011-07-19

Filed under: Posts — Tags: — Jesper Kristensen @ 11:00 pm

Platform/2011-07-19


« previous week | index | next week »

<script>if (window.showTocToggle) { var tocShowText = “show”; var tocHideText = “hide”; showTocToggle(); } </script>

Notices / Schedule

  • The Firefox 3.6.20 (used to be called 3.6.19, which was then used by the 10.7 out-of-band release) schedule is now posted
    • Shipping at the same time as Firefox 6 (August 16)
    • Code freeze for non-blockers: 2011-07-25
    • Code freeze for blockers: 2011-08-01
  • Check out Johnath’s post (also on the channels blog) detailing the release schedule if you are unclear

Firefox Development

  • Telemetry work for front end bug 671038
  • Drew’s dynamic e10s analysis work has r+, but there’s a crasher in mochitest that needs debugging before he lands it bug 666713

GFX

  • Cross-origin WebGL textures using CORS (bug 664299) landed last week (and a bug in the implementation, bug 671906, landed over the weekend).
    • WebGL Angry Birds works again!
    • Note: DO NOT VISIT THAT LINK YOU WILL NEVER DO ANY WORK AGAIN

JS

  • IonMonkey ran its first program, a tiny program with a & operator.

Layout

  • New platform hires:
    • Scott Johnson — layout
    • Ralph Giles — video/RT
    • Randell Jesup (“new”) — RTC/general
    • Mats Palmgren (“”new””) — layout
    • Jean-Marc Valin — codecs

Plugins

DOM

Network

Accessibility

Multi-Process

Electrolysis/Short-Term Goals

  • Firefox starting up landed to m-c: set pref “browser.tabs.remote” to true to try it out!
  • Windows accessibility experiment appears to be successful: we’re using a dummy window to provide the accessibility tree and NVDA appears to be able to navigate it
  • Discussion about responsiveness metric ongoing: are we going to measure UI interactions such as new-tab and new-window, or content effects on responsiveness, or both?

Tree Management

  • Starting Wednesday morning, we will only generate nightlies when something has changed
    • If no code change and no locale string change for any locale, then do not generate new nightlies.
    • If any code change, or *any* locale change, we’ll still generate new nightly builds for *all* locales.
    • details in bug 650258
    • This means no updates for aurora unless there are code/l10n changes. Need to advertise this on the channels blog?

Stability Report

Roundtable

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress