Firefox3.1/StatusMeetings/2008-09-03

From MozillaWiki
Jump to: navigation, search

« 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 x91 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 2.0.0.17 / 3.0.2

  • have had a few respins on both branches, but builds are becoming available
  • these delays have resulted in some proposed schedule changes
    • Tue, Sept 9th - QA signoff & go to beta
    • Tue, Sept 16th - QA signoff on beta & release

Firefox 3.1

  • New on the trunk this week:
    • updated TraceMonkey
    • some Worker Threads stuff coming up this week
  • if you've got a new feature landing, please point it out on the web tech blog
  • Alpha 2 Schedule
    • builds out to QA
    • QA expects to sign off this week by Friday
    • not planning on updating 3.1a1 users to 3.1a2
  • Beta 1 Schedule
    • code freeze now Sept 30th
    • tracking against this in development meetings

Support

Top Issues

  • startup crashes like bug 434403 and bug 401513 (google desktop) are most frequent reports
  • showing bookmarks in awesomebar results by default is seen as a privacy issue -- people don't seem to understand what they're seeing
  • some users are experiencing locked profiles after Major Update; seems to be related to Norton 360

Localization

temporary build bots 
running at bsmedberg's home, upload not nifty. All builds reporting to Mozilla-l10n, locale-specific steps report to l10n tinderbox pages, too. No compare-locales yet. Builds uploaded on latest-mozilla-central-l10n ftp
localization update 
From the dashboard,
  • 20 locales landed fx changes
  • 4 tier 1, minus en-GB, ja
  • only 6 out of 14 in tier 2
  • new locales in 3.0.2 landing on l10n-central soon (+8)

QA

  • Release discussions. Was it too much cramming in 4 releases in the same month? (MU, 2.0.0.17, 3.0.2, 3.1a2)
    • Concern of work overload led to simple mistakes
    • Maybe timing was just bad, with Competitor pressure + vacations?
    • Examples: bug 316859 comment 23 - forgot to track regression, bug 446527 comment 87 - automated testcase not catching errors, Fx3.0.2 requiring 4 respins - empty updater.ini file on linux/mac
  • 2.0.0.17 (Juanb)
    • Testplan can be found here
    • verifying a few 20017 bugs and gonna try to do updates on betatest today, when they become available.
  • 3.0.2 (QA lead Tomcat)
    • Testplan can be found here - Beta release ETA: September 9
    • Build 4 Mac and Linux Builds are currently tested by QA
    • Signed Windows Builds are available later today and QA will testing this builds as soon as they are available
    • The other tests (Updates) will follow
    • QA continues the Bug verification of the Bugs fixed in 3.0.2
  • 3.1a2
    • alpha 2 Testplan results posted
    • What's left, spot checks on Linux and Mac. smoketests pass.

Build

  • FF2.0.0.17: 2 respins
  • FF3.0.2: 4 respins
  • l10n build boxes
    • bsmedberg using modified .ssh keys as interim
    • need release automation working on buildbot+hg

Evangelism

Marketing/PR

Roundtable

  • bug 448616 - no symbols for 3.1 builds; seems to be a XCode problem, being worked - getting critical
  • bug 433710 - graph server doesn't show memleaks; patch awaiting review done
  • if you need icons produced please tell faaborg