Firefox2/StatusMeetings/2006-05-23

From MozillaWiki
Jump to: navigation, search

<< previous week | index | next week>>

Meeting Details

  • 11:00am PDT (18:00 UTC)
  • Mozilla HQ, 1st floor conference table
  • +1 866 216 2181 (or +1 303 228 0514)
  • join irc.mozilla.org #bonecho for attendance taking

Agenda

  1. Bon Echo Alpha 3 Planning
    1. status update (SafeBrowsing, DOMStorage, NSIS, JS 1.7?)
    2. review remaining blockers & nominations
  2. Development Roundtable
  3. Any other business

Bon Echo Alpha 3

  • status updates (DOMStorage, JS Fast Load, SafeBrowsing, JS 1.7, NSIS)
    • tony: most of the balsa leak regressions are taken care of, seeing some around loading JS components, but that might be a leak, patch pending for Tp
    • mconnor: talked to brendan yesterday, seems very confident of the Wednesday target
    • rstrong: having problem with the post-build tinderbox scripts, and there are some minor patches to the scripts, looks like we're running the make-installer twice, though, so that might have something to do with it. Built both on trunk and branch without any issues, so this seems to be a tinderbox issue, not exactly sure.
  • blocking bugs: blockers & nominations for alpha 3
  • other pieces: UndoCloseTab, TabOverflow
    • dietrich: UndoCloseTab is blocking on sync of branch and trunk of session restore (minor JS and leak fixes); once that lands, we can land UndoCloseTab
      • mconnor: should have that done tonight or tomorrow
    • mconnor: TabOverflow is going to have to move to Beta
      • dietrich: will that include the new tab open/close notifications?
      • mconnor: yes, this will make real events for tab open/close
  • rstrong: how to people feel about bug 335864
    • bsmedberg: this could wait until beta, or land today at the latest
    • mconnor: low risk enough to take, but file a followup filed to change where we directly set the pref to use the appropriate methods
  • proposed schedule
    • now and onwards: closed tree, mconnor/cbeard manage A3 approvals
    • Wednesday, May 24th: land JS 1.7 patches on the branch
    • Thursday, May 25th: freeze for Alpha 3 (noon PDT)
    • Friday, May 26th: ship Alpha 3
  • bsmedberg: which builds will be the A3 candidates?
    • mconnor: I expect JS 1.7 things to break a little
    • beltzner: the first set of candidate builds will be the ones after code-freeze at noon PDT on Thursday
  • a reminder from last week ...
    • schrep: there is no Alpha 4; we had Alpha 3 for the P1s that we couldn't ship without. Those critical path features are the primary ones which everyone should be paying attention to for the next while, since pushing A3 back pushes our release date back further and further and we should avoid that at all costs.

Developer Roundtable

Please add any status updates from the past week, including links to relevant bugs, newsgroup discussions, etc:

Visual Refresh: Chrome Polish

  • walking through some end-to-end scenarios to find polish bugs for B1/B2
  • should have these filed early this week (will use [meta] keyword)

Visual Refresh: Theme Polish

  • one of our vendors has asked for more time, so I can't show anything yet, but will do so as soon as possible
  • an interesting thing to think about is: what does "native look and feel" mean for Windows Vista? The only apps which seem optimized for Vista's new UI are Office 12 and the shipped-with-Vista apps (Notepad, Explorer, etc). Will other apps (like Adobe) follow suit? Hard to tell, so it's hard to tell how much we'll have to in order to avoid looking old and busted.

Bookmarks and History: Places

User Experience: General & Tabbed Browsing

User Experience: Session Restore

User Experience: Spell Check

Most critical bugs fixed. The tracking bug for the remaining issues is bug 338999. We should start making the web page for dictionary download.

User Experience: Microsummaries

Feeds: Parser

Feeds: UI

Extension Manager: UI

Extension Manager: Blocklisting

Extension Manager: Locale Packs

Search: UI

Search: Plugin Format

Distribution: Installer

Distribution: EULA

Distribution: Channel Support

Infrastructure: Performance

Infrastructure: Platform Uplift

Infrastructure: Instrumentation

Security: Phishing

Security: SSL

User Documentation

Developer Documentation

L10n

  • received feedback for zh-TW
  • filed bug 339000 to track l10n workload
  • got some initial tracking on trademarks at XTech, posted to .planning and .firefox
    • cbeard: take offline, got some initial drafts
  • beltzner: if there are large string changes, how much time does your time need?
    • axel: try to get it done 2 weeks before B1 code freeze, which is June 6th, would be nice
    • mconnor: what are the big string hits for Fx2? let's optimize that critical path
      • feeds
      • safebrowsing
      • searchplugin manager
      • spell check
      • preferences

Other Business

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox2/StatusMeetings/2006-05-23&oldid=26731"