<< previous week | index | next week>>

Meeting Details

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

Agenda

1. Bon Echo Alpha 2 (Tracking & Status)
2. Development Roundtable
3. Any other business

Bon Echo Alpha 2

We're in the final push for Alpha 2. During this meeting we'll triage the following items:

• Bon Echo Alpha 2 tracking bug: bug 337193
  • SafeBrowsing has severe Ts regressions, was backed out this morning
  • sessionsaver and mozstorage are also causing problems
  • we're diverging from the trunk which has been closed while we jammed a bunch of stuff into the alpha at the last minute
  • paths are:
    • delay A2
    • get stable A2 and ship it feature-reduced
    • plow ahead and fix these issues until they're fixed and then sync back to trunk
  • timeless: XULRunner and Seamonkey are also broken
  • dveditz: I'm also nervous about feeds being a chrome priv'd page
  • schrep: we need to have a hard deadline for this Friday

• blockers(bugsmarked blocking-firefox2?/+ or blocking-1.8.1?/+ with a target milestone of "Firefox 2 alpha2" or "mozilla1.8.1alpha2")
  • triaged the list, moved a bunch of stuff to beta 1

Then we'll run down the list of what made it in for compiling the release notes. The current list is:

• session restore
• microsummaries
• spell checking
• feeds
• extension manager
• search manager
• search box enhancements
• search suggestion infrastructure
• new ciphers (ECC)

Developer Roundtable

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

Visual Refresh: Chrome Polish

Visual Refresh: Theme Polish

Bookmarks and History: Places

User Experience: General & Tabbed Browsing

User Experience: Session Restore

• Landed and enabled on branch and trunk
• Ts: Some Ts hit, but not clear to what extent because of so many checkins before freeze. Yesterday we pushed file handling until first window's onLoad, which seemed to help on Mac/Linux, but had no effect on the Windows tinderboxes. It might be worth disabling the service for a few builds to get a clearer picture of the actual impact.

User Experience: Spell Check

User Experience: Microsummaries

Feeds: Parser

Feeds: UI

In & On, no perf regressions that I could see

Focus post a2: - best architecture for security - UI adjustments - Sniffer adjustments

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

zh-TW: team responded, gonna take over for piaip, who's lost in military service. No idea about sim-ship, but best alternative available.

Other Business

• timeless: can we get multiple tinderboxes going so we can do Ts checking out of the mainline?
• schrep: we're working on getting the build farm up to speed, but this will just take some time; the goal is to move a lot of the tinderboxes to VMs and get them on a cluster
• schrep to ping myk and timeless on regressions
• tony: so does feature reduced A2 mean that we're shipping an A3?
  • beltzner: I'm a little nervous about putting large features that caused these problems in A2 into B1 for the first time
  • schrep: we can do whatever we want, but another Alpha will have an impact on our final ship date
  • perhaps we can do a short cycle A2 and spin out an A3 at the end of the month
  • need to figure out how significant the Ts regressions are and how hard they'll be to fix
  • reminder: not planning to auto update A1->A2