Mobile/Notes/19-Aug-2009

Details

• Wednesdays - 9:30am Pacific, 12:30pm Eastern, 17: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

Application

General Front-end

• Lots of work getting tile cache regressions/breakage fixed (bug 509381)
• Landed a few new features too
• Waiting for beta 3 to release before landing more stuff
• Working with Madhava to get any strings landed so we can make a string freeze soon
• UI changes
  • Sidebar behavior: only "New Tab" action will close a sidebar
  • Bookmark editor: lightweight popup appears before the main panel

UX design

• ongoing work on start / first-run / web-stuff with marketing
• working with weave team; getting a preview of 0.6 to try out
• otherwise, see above (front end)

Platform Support

Windows Mobile

• 20 bugs blocking final release http://bit.ly/blocking-wm
• 1 bug blocking alpha 3 http://bit.ly/blocking-wma3 (which I think can be closed)
• tile cache is a nice perf win
  • seeing 5-11s pauses whenever the checkerboard shows up
    • DrawWindow taking 70-200ms (per tile)
• need to make a decision on browserd
  • crowder seems reasonably confident that it can land in two days
  • this is a good release with or without it

General Back-end

Video

Integrated the element we got from the GStreamer comunity - we now have much better framerate on the N810 (still not great - but better)

Still some bug(s) in the integration that prevents more than one video per session.

Camera

• still waiting for reviews (got one from dougt)
• nino will be working on implementing support on OSX and Windows

Builds

• desktop builds
  • linux already available
  • osx packaging issues. possibly just land win32.
• stabilizing and dealing with load
  • we have 15 n810s in production pool today
    • 1 push every 4 hours will occupy 10 n810s. (approx, depending on if build fails, tests run to completion, etc, etc).
    • 1.5 pushes every 4 hours will occupy all 15 n810s
    • 7 pushes every 4 hours was the average for July.
  • waiting 20 more n810s in transit - ETA next week
    • all donations accepted!
  • reducing load: changing unittests-per-checkin on fennec-on-desktop builds, not on the n810s. continue to run unittest-on-nightly on n810s. reduce talos runs.
• WinMO: Need help getting unittest, talos running on WinMO manually, before we can do automation.

QA

• What to do about our tracking bugs for the failing tests on maemo: bug 473558 (mochitest failures) and bug 473564 (reftest failures)
  • These tests have been failing and bugs have been filed for the better part of a year.
  • We believe that these should block 1.0.

• Bugs we want for beta 3
  • bug 481950 (unable to enter passwords with caps or fn key on maemo)

• Bugs failing smoketests/BFT's:
  • Saved form information bug 466770
  • Acid2 test bug 499388
  • Panning with multiple tabs bug 476703

• QA Companion on Fennec
  • First run will be a small add-on to help community members file bugs on Fennec
  • Will probably put bugs into Linux/Maemo and Windows Mobile component based on what the person is running.
  • The bugs will have [QAC Generated] pre-pended to the summary for easy tracking and triage.
  • What else do you want to see in such a tool?

• QA Execution
  • We need traction on the Round Robin Schedule within MV
    • Since everyone in Mobile and Mobile-QA seems to have at least one device, I'd like to suggest opening this up to everyone in MV
  • How do we handle re-directs to m.whatever.com when they start to occur?
  • What's the timetable on when components will be distributed among elements of the Fennec UI on Bugzilla?
  • need to define what QA will do for l10n for Beta4 and 1.0 release?
    • how many languages are out there?
    • what type of QA will the translators do and what platforms will the QA on?

Other

• WinMO beta will need updates. ETA of beta is end Sept2009. RelEng to investigate what is possible.