Meeting Notes Meetings notes from the Mozilla community

25-November-2010

Mobile Meeting Minutes: 2010-11-24

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am

Mobile/Notes/24-Nov-2010

From MozillaWiki

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • irc.mozilla.org #mobile for backchannel

Schedule

  • Beta 3
    • Code freeze: Nov 23 (slushy)
  • Beta 4 (need dates)

Major Topics for This Week

  • Wrapping Beta 3
    • Remaining b3 blockers
    • Sync/JPAKE
    • Content Crash Reporting
    • L10N / Packaging
    • IME regressions

Front-end

  • Beta 3 stuff
    • Sync/JPAKE
    • Content Crash UI
    • IME Regressions
  • Moving ahead to b4 blockers and final blockers
    • Final blocker list will be triaged next week. Anything pushed will be moved to the next release (post 4.0)

UX design

Maemo

Qt

Android

  • Keyboard fixes landed (bug 599811, bug 581596); some regressions being worked on.
  • still waiting for packaging and multilocale repack stuff

Electrolysis

General Platform

Video

Camera

Plugins

Performance

Networking

Graphics

Startup

Layout

Content

Release Engineering

QA

  • New Bugs over the week: filed. Still at 16 blockers
  • Cross-browser Performance tests are done. Check out the results
  • Working on defining a Device Compatibility testplan for beta 3+. Work in progress.
  • Results from nightly Smoketest runs
  • Input: Manufacturer and Device are being sent to staging database and registering those fields correctly. Next step is to make it available on the dashboard.

Automation

  • first regression was found and fixed on maemo mochitests!
  • I have a local fix for xpcshell on n900, will roll out next week in staging when releng starts coming back online
  • talos patches have landed for android fixes, installs are working but some devices are failing (investigating ways to reduce hung boards)

Other

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress