Personal tools

Platform/2010-08-17

From MozillaWiki

Jump to: navigation, search

« previous week | index | next week »

Contents

Notices / Schedule

Firefox 4 Beta 4

  • mostly code frozen
    • two late regressions will be fixed on relbranch
    • should have builds late today, PT
  • puts release target as next Monday, Aug 23

Firefox 3.6.9 & 3.5.12

  • We are frozen!
  • Thanks everyone for the good convergence
  • Will be clearing/pushing forward approvals to the next version in the coming week
  • Verifications/testing now until the 23rd, then a build

Firefox 3.6.10 & 3.5.13

  • Start nominating!
  • Not approving bugs yet as we don't have a branch ready for landings

Blocker Report

Firefox 4 Beta

Firefox 3.6.9 & 3.5.12

  • We are frozen!
  • Thanks everyone for the good convergence

Firefox Development

(from our goals):

  • [ON TRACK] Feature complete Firefox 4
    • [DONE] Switch to Tab
    • [DONE] App Tabs - Scope for 4.0 reduced (non-global), near feature complete.
    • [DONE] Extension Manager - Bug list is converging, still a lot of work to do.
    • [DONE] Web Console
    • [ON TRACK] Notification UI - Geo and EM notifications done, http auth next.
    • [ON TRACK] New Theme - Windows and Mac good, Linux catching up now
    • [DONE] TabCandy Panorama
    • [AT RISK] Silent updates on Windows
    • [DROPPED] Inspector
    • [DROPPED] Account Manager - WIP patches posted, but we can't contain the review load and code risk.
  • [AT RISK] Dirty profile startup within 20% of clean profile startup (modulo extensions, plugins; on windows)
    • Current status: Lots of data has been collected and analyzed, but no solid conclusions have shaken out.
    • Details page
    • Shawn has an updated blog post. Read it for more info.
    • Bugs on file that help:
      • Excessive cookie i/o bug bug 572223 (fixed)
      • Session Restore negatively impacts startup time based on the number of tabs loaded bug 582005
      • Suboptimal SQLite page size bug 416330 (fixed)
      • Provide a global VACUUM component bug 541373


Platform

(there is a team-by-team goals breakdown, as well)

  • [DONE] Javascript performance near or even with Chrome 5 on their benchmarks (within 20% on SS, 30% on V8), with substantial wins on our benchmarks. (Windows, in-browser.)
  • [DONE] Hardware acceleration of video and other HTML and SVG content, as well as user interface, on by default for compatible hardware on all Tier-1 desktop and mobile platforms.
  • [DONE] Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES.
  • [MISSED] security: zero reproducible high/crit > 30 days
  • [DONE] Support multi-process Fennec.
  • [DONE] Support Jetpacks running in separate processes and never blocking the Fennec UI. NOTE: jetpack team hasn't actually integrated this code yet, but it works in small test environments.


JS

Plugins and Multi-Process and Such

Areas of concern for betas/feature freeze:

  • asynchronous plugin painting, bug 556487
  • 32-bit plugins in 64-bit Firefox, bug 559142
  • Plugins withstand app-tab reframing or dragging a tab to a new window, bug 90268

GFX

  • D2D status:
    • Direct2D is not turned on by default for Firefox 4 beta 4. (We weren't confident enough to turn it on for all users.)
    • However, all the code in Firefox 4 beta 4, and it should work reasonably well for everyone.
    • We really need testers, both on the beta and on nightlies. (We plan to enable Direct2D in nightlies as soon as beta 4 is tagged and branched.)
      • To turn on Direct2D: Go in to about:config and set mozilla.widget.render-mode to 6, and gfx.font_rendering.directwrite.enabled to true.
      • To turn off Direct2D, once it is on by default, set mozilla.widget.render-mode to 0.
      • To check whether you are running with Direct2D, go to about:support and look at the bottom. (Once bug 586046 lands, there will be even more information about your graphics card in there.)
      • Please look out for memory usage, rendering speed, and any rendering problems you might see. Also focus on interactions with plugins like Flash.

Layout

  • Bug 130078 progress (goal)
    • Bug fixes keep coming, fixing tryserver test failures
    • Expecting to land next week, but Timothy may need help over the next few days
  • Cool stuff landed
    • -moz-element
    • mozRequestAnimationFrame
  • More stuff ready to land
    • DPI changes (mozmm unit for mobile)
    • SMIL event-based timing
      • Almost completes our support; "accesskeys" only remaining feature of interest

Video

  • Landed 'buffered' (goal)
    • Implemented for Ogg and Wave
    • WebM returns no buffered ranges currently, but the basic implementation is nearly complete
  • More stuff ready to land
    • 'autobuffer' -> 'preload' (spec compliance)
    • New load algorithm (spec compliance)
    • Integrated scaling + YUV conversion code (performance)
    • Switch controls to use 'buffered'
    • Make media events not be progress events (spec compliance)

Content

  • Big thank you to jduell, dwitte, mayhemer, jdm, for getting the last e10s necko fennec a1 blockers fixed and landed!
  • HTML5 form control work nearing completion (for fx4). If you get review requests relating to HTML5 form controls, please help out, or let people know so we can find others to help out!

Tree Management

Roundtable

  • QA Focus Areas for Beta 4 (juanb)
  • Please don't forget to mark developer documentation-impacting bugs with the dev-doc-needed keyword in Bugzilla!