Firefox3.1/StatusMeetings/2009-02-11

« previous week | index | next week »

Firefox Product Delivery Meeting Details

  • Wednesdays - Firefox 3 - 11:00am Pacific, 2:00pm Eastern, 18:00 UTC
  • Mozilla Building S
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • irc.mozilla.org #shiretoko for backchannel

NOTE: See Platform#Meeting_Notes for development meeting notes

Firefox 3.0.x

(Quietly...)

Firefox 3.1 Development

Development Update

Daily users (weekly average across versions)

  • 3.1b2 -
  • Shiretoko -
  • Minefield -

Beta 3

Support

  • Top 3.1 issue is bug 4775653 (Enter key doesn't work in address bar, AVG Safe search 8.0.2333). How do we get evangelism on this?

Localization

  • Mongolian landed during FOSDEM
  • l10n-drivers started to talk about bottlenecks in current tasks and processes, initial ball mark could be 80
  • Talked about potential collaborations between Silme and other FOSS l10n infrastructure tools at FOSDEM

QA

  • Financial Institution page is up. Please signup to test on Firefox 3.1 nightlies!
    • Public site (Anonymous - please don't add yourself here)
    • Intranet site (Internal coverage)
      • Tip: If websites are not rendering or loading correctly on the nightlies, be sure to follow these steps first before reporting a bug.
  • Firefox 3.0.6 -> 3.1b3 Trial Run awaiting b3 builds first
  • Firefox 3.1 Feature testing progress:
    • Testplans (93% completed)
    • Testcases (85% completed)
  • 29 1.9.1 bugs verified last week
  • New OS support
    • Windows 7 beta VM is available for testing
    • Now have a copy of Snow Leopard (OSX 10.6), in the lab

Release Engineering

Nothing from us this week.

Add-Ons

Partners

Evangelism

Marketing/PR

Roundtable

  • justin agreed to follow up with morgamic to ensure that we could throttle Major Update snippets on a per version / channel basis (to allow users to "Check for Updates..." to Firefox 3.1 on launch day, but not have the offer given to users who do not explicitly check) <-- This is bug 475145. Should that be marked blocking-firefox3.1+?