Platform/2010-08-17

From MozillaWiki

« previous week | index | next week »

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

• a handy list of triage queries is available for all!
  • Beta 5: 94 blockers
  • Beta N: 237 blockers
  • Final: 234 blockers (571 total)
  • nominations: 290 nominations

Firefox 3.6.9 & 3.5.12

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

Firefox Development

(from our goals):

• [NEW] Feature complete Firefox 4
  • [DONE] Switch to Tab
  • [ON TRACK] Extension Manager – Functionality there, lots of bugs to fix.
  • [ON TRACK] Notification UI – Geo done, patches on follow up bugs.
  • [ON TRACK] New Theme – Substantially done on Windows and Mac, Linux lagging.
  • [ON TRACK] App Tabs – UI in place, functionality follow ups to get to feature complete
  • [ON TRACK] Silent updates on Windows
  • [ON TRACK] TabCandy – Landed, but lots of follow up work to do on interactions, integration with other features
  • [AT RISK] Account Manager – Not currently blocking, but Dan Mills and co. are racing to get there.
  • [AT RISK] Inspector
  • [AT RISK] Web Console

• [NEW] Dirty profile startup within 20% of clean profile startup (modulo extensions, plugins; on windows)
  • Shawn has an updated blog post. Read it for more info.
  • Excessive cookie i/o bug bug 572223(fixed)
  • Session restore bug 582005
  • Still looking for more pathological profiles

Platform

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

• [ON TRACK] 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.)
• [ON TRACK] 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.
• [ON TRACK] 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.
• [ON TRACK] security: zero reproducible high/crit > 30 days
• [ON TRACK] Support multi-process Fennec.
• [ON TRACK] Support Jetpacks running in separate processes and never blocking the Fennec UI.

JS

• Landed YARR
• ES5
  • Landings
    • Made ES5 test suite work with javascript.options.strict set to true
  • To land once reviews (sometimes of dependent bugs) occur
    • Requiring exact argument count for getters/setters in bug 536472
    • Poison-pill for fun.caller and for arguments.caller and arguments.callee
    • JSON stringification bugfixes
    • Make arguments copy initial argument values (and not alias named parameters) in strict mode
    • Date.prototype.toJSON isn’t to spec
    • Implement Function.prototype.bind
  • In progress
    • …

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

• TryServer “roast” in 10Forward at 11.30 – right after this meeting
  • details [ http://groups.google.com/group/mozilla.dev.tree-management/browse_thread/thread/1d517814b6e43324# ]

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!

Platform/2010-08-10

From MozillaWiki

« previous week | index | next week »

Announcements

• Firefox 3.6.4 post-mortem is this Thursday, 2010-08-12 @ 11:00 am PST. More information is here.
• Continue to focus on blockers.

Tree Health

Three things must improve:

1) Mistakes must be less costly. This means faster build machines, faster infrastructure. We’re making progress here.

2) We must make fewer mistakes on shared infrastructure. Totally unacceptable: checking in and failing every build or leaking on every test, on every platform. This goes for TryServer as well: it is not your compiler. Be respectful of other people’s time.

3) Check to see if the tree is orange before checking in. Sheriffs are going to start backing people out for doing this because it’s rude and may end up closing the tree because orange got landed on top of orange. When in doubt, ask the sheriff.

Additionally, we’re looking at separating some work onto separate repos, with the same rules as mozilla-central, in order to reduce traffic on mozilla-central.

Feedback here mozilla.dev.platform thread.

Notices / Schedule

Firefox 4 Beta

• Beta 3 should hit QA signoff later today, will release tomorrow
• QA’s beta 3 bugs for those interested
• Beta 4 code freeze scheduled for next Monday
  • would like all major landings to be complete by this Friday, though (see Roundtable)
• feature freeze still scheduled for Beta 5
  • a “feature” is any code which creates a new or makes a significant change to existing interactions between the user and the browser, developers and browser APIs, or web authors and the browser
  • after feature freeze we will only be stabilizing and polishing

Firefox mobile (alpha)

• CODE FREEZE IS TODAY
• Bug list

Blocker Report

Firefox 3.6.9

• There are 26 open blockers (+4 w/w)
  • Code freeze is currently scheduled for Thursday August 12 @ 11:59 pm PST
  • Let’s try to not get them all in on the last day. I’ll be bugging people furiously this week and the start of next
• Only approving blockers at this point

Firefox 3.5.12

• There are 16 open blockers (+3 w/w)
• Code freeze is tied to 3.6.9

Firefox 4 Beta

• a handy list of triage queries is available for all!
  • Beta 4: 56 blockers
  • Beta N: 218 blockers
  • Final: 232 blockers (559 total)
  • nominations: 275 nominations (153 OPEN)

Firefox Development

(from our goals):

• [NEW] Feature complete Firefox 4
  • [DONE] Switch to Tab
  • [ON TRACK] Extension Manager – Functionality there, lots of bugs to fix.
  • [ON TRACK] Notification UI – Geo done, patches on follow up bugs.
  • [ON TRACK] New Theme – Substantially done on Windows and Mac, Linux lagging.
  • [ON TRACK] App Tabs – UI in place, functionality follow ups to get to feature complete
  • [ON TRACK] Silent updates on Windows
  • [AT RISK] Account Manager – Partial work, restaffing to get this one done.
  • [AT RISK] TabCandy – Reviews done on standalone pieces like iQ. Reviews pending on patches that touch browser code.
  • [AT RISK] Inspector
  • [AT RISK] Web Console
  • [AT RISK] Integrated Sync – Landed, activation caused leaks, Sync team (mconnor, ragavan) owns this.

• [NEW] Dirty profile startup within 20% of clean profile startup (modulo extensions, plugins; on windows)
  • Shawn has a blog post with preliminary data
  • Session Restore is the biggest single culprit
  • Bugs filed for session restore bug 582005 and excessive cookie i/o bug 572223(fixed)

Platform

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

• [ON TRACK] 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.)
• [ON TRACK] 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.
• [ON TRACK] 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.
• [ON TRACK] security: zero reproducible high/crit > 30 days
• [ON TRACK] Support multi-process Fennec.
• [ON TRACK] Support Jetpacks running in separate processes and never blocking the Fennec UI.

Layout

• bzbarsky has implemented JS animation API that can keep in sync with transitions/SMIL etc
  • Very simple, should land shortly
• bug 130078 making progress, many parts landed
• We’re not testing retained layers very well on tinderbox machines: screen sizes mean our windows are too small to display entire reftest, so reftests don’t grab data from the retained layers

Video

• Landed ‘buffered’ support for Ogg/WAV
  • Patch in hand for basic WebM ‘buffered’ support, will follow up with optimizations
• Will set up a test machine to compare Flash with our video under controlled conditions

JS

• JM conformance and perf continues to improve
• YARR regex lands this week on TM and MC
• ES5
  • No landings this week, but now awaiting review on bug 514581, bug 514563, bug 584909, bug 585803, bug 438633 and very nearly bug 516255
  • Current work
    • Requiring exact argument count for getters/setters in bug 536472
    • Poison-pill for fun.caller and for arguments.caller and arguments.callee
    • Make arguments[i a copy of that initial parameter, not a reflection]
    • JSON stringification bugfixes
    • Killing an extra warning for duplicated property names

Windows 7 Test Status

Tree Management

• Tinderbox woes
  • Read Ben’s blog for current status and plans to make things better.
  • Rebalancing pool size – moving some machines from production to try
  • 10.6 builder upgrades in progress – should be unblocking buildsymbols today/tmrw

Roundtable

• <sayrer> Meeting starts at 11:00 PT. Be here on time.

• <beltzner> New milestone code freeze process
  • For Beta 3 we tried to land Firefox Sync. We failed to check assumptions about previous performance and unit testing, which left us in a bad state on Monday and eventually slipped the code freeze. Lots of things learned about tryserver (which can and should be used to pre-evaluate large landings!) and the implications of committing early to a feature in a specific beta in the ensuing investigation.
  • TraceMonkey merge caused some functional regressions that required respins and delayed beta ship – hard to see due to intermittent test failures and number of landings
  • We need to have a solid tree the weekend before a planned code freeze, with any major landings having been tested for performance and functionality before Friday and landing by Friday end of day. Anyone who lands after Friday *must* stay around to ensure there are no performance or test regressions in their code.
  • Suggested new process
    • Code stabilization on Friday, end of day PT
    • No new strings between stabilization and freeze
    • Only bugfixes between stabilization and freeze
    • Everyone must monitor full tests after checkin between stabilization and freeze
    • Freeze Monday midday PT following code stabilization
  • this process was generally agreed-upon at the meeting

• <blizzard> UA changes – get them done now
  • dwitte to file a blocking bug and drive the process through bug 586165

• <bsmedberg> wants to discuss the following blocker nominations
  • resource packages bug 529208: no cross-browser spec, concern about whether it will actually improve perf, questions about whether it will be deployed with a moz Prefix or not, and little or no reviewer time to actually take it
    • performance improvements in plone show up to 25% page load improvement (jonas)
    • feels like we should be making a push to take this one, and it would be a bummer if we couldn’t get it (sayrer)
    • no decisions made about how to resource it
  • desktop omnijar bug 556644: the current plan involves repacking locale files, which is going to require lots of testing and regressions may show up late. I’m very concerned and if it is a blocker we need better ways to mitigate risk.
    • very valuable win on startup time (shaver)
    • felt that this needs to be a blocker, people need to file blockers on the follow-up issues

• <beltzner> Using Tryserver
  • investigation from Sync showed that Tryserver successfully predicted test failures and may have predicted Talos regressions – it’s just that nobody looked
  • tryserver now faster (though wait time on Windows can still be high)
  • uses same test infrastructure as mozilla-central
  • releng very interested to hear why developers aren’t using it, how they can help
  • joduinn to schedule follow up meeting
  • in the meantime, you can always leave a suggestion about what could make it easier for you to use the infrastructure

• <stuart> Getting Reviews
  • It is taking an awful long time to get initial reviews for many blocking fennec bugs. Are people not looking at them, or using bad queries?