Firefox2/StatusMeetings/2006-06-20

<< 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 backchannel

Agenda

1. Bon Echo Beta 1
   1. Setting up triage meetings, criteria
   2. Any scheduled landings?
2. Development Roundtable
3. Any other business

Bon Echo Beta 1

Links to bug lists:

• blocking-firefox2+ && tm=Firefox2 Beta1
• blocking-firefox2+ && tm=Firefox2 Beta2, Firefox2
• blocking-firefox2?
• blocking-mozilla1.8.1+
• blocking-mozilla1.8.1?

Current target dates:

• June 15th: major string changes in for l10n to start
• June 19th: tree locked to branch approval flags only, daily triage starts
• June 27th: Beta 1 Code Freeze at 11:59 PDT (some QA begins)
• July 6th : Beta 1 Ship
• the schedule is available as an ICS file or on this page

• need to set up times for triage/landing approval calls
• are there any large landings that need advance scheduling?

Developer Roundtable

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

User Experience: General & Tabbed Browsing

• beltzner: I'm a little behind, including a couple of bugs that will likely have l10n impact. The areas where I still have design decisions owing are:
  • automatic update experience bug 334767 (est. 1d worth of implementation)
  • major version change update experience (est. 2d worth of implemementation)
  • firewall problem after update (est. 1d worth of implementation, major l10n impact)

User Experience: Microsummaries

• fixed two bugs (337825, 341555) with UI impact;
• large patch in third bug (339543) reviewed by biesi, awaiting addl. review by mconnor
• six P1 beta1 bugs with swag of 7 days -- working on these this week and weekend
• six P2 beta1 bugs with swag of 5 days -- at risk
• four P3 beta1 bugs with swag of 12.5 days -- will be retargeted to beta2 or Firefox 3
• followup security review this afternoon at 3pm PDT

Developer Documentation

• Search-related docs are finished.
• Still pending:
  • Session restore API
  • Feed content access API
  • Writing phishing protection extensions
  • Best practices for extension versioning
• If you have information an any of those, please email [Sheppy].