Firefox3/StatusMeetings/2007-01-17

From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Meeting Details

  • 11:00am PST (19:00 UTC)
  • Mozilla HQ, 1st floor conference table
  • 650-903-0800 x91 Conf# 217 (US/INTL)
  • 1-866-879-4799 (pin 369) Conf# 217 (US)
  • join irc.mozilla.org #granparadiso for backchannel

Agenda

  • Action items
  • Gecko 1.9 Alpha 2 Planning
  • Gecko 1.9 Roundtable
  • Firefox 3
  • Any other business

Gecko 1.9 Alpha 2 Planning

  • Linux ref platform status
  • units unification (bug 177805) status (campd was going to help out on OSX?)
    • campd tested on linux, had some issues, still working on it
  • cycle collector performance status
    • jonas says the patch landed, and helped, but we're not back to where we started (now at 5%)
  • new textframe/textrun code (bug 333659)
    • landed, new textframe turned off
    • got backed out, had windows problems
  • jst uber security hardening patch status (bug 355766)
    • still waiting for reviews (bz to look at it this week)
    • have testing builds generated now, should get some testing from that
    • should be landed by early next week

Gecko 1.9 Roundtable

  • Gecko 1.9/Firefox 3 triage plan
    • details will be posted to dev planning soon
  • platform optimization flags review
    • schrep still to look into it
    • dbaron switched tinderbox to using -Os and got a win on both codesize and perf

Testing

  • Tp test framework status
    • problems with trunk fixed
    • tests ran successfully on branches and trunk, results sent to graph server
    • alice will circulate link to graph server
  • buildbot status
    • blocking on fedora VM for master
    • windows slave VM ready to go
  • test harness inventory in progress

Firefox 3

  • not enough time for full walkthrough at this meeting
  • PRD has reworked section for evaluation of requirements/goals
  • feedback requested on any missing major functional areas from product plan
    • rob says no mention of feeds in PRD
      • will be addressed as part of content management, along with microformats and streams of microformats
    • shaver mentions a cross-cutting concern for testability
    • bsmedberg asks about offline web apps support
  • mconnor to break up discussion into functional areas
    • meetings to take place over next week and a half
  • can we figure out what are the P1/P2's that we are confident about, so that we can prioritize and get people on these while we work through the less concrete elements?
    • will do a quick pass over the list to identify those pieces

Any other business