Meeting Notes Meetings notes from the Mozilla community

14-July-2010

Mobile Meeting Minutes: 2010-07-14

Filed under: Posts — Tags: — Jesper Kristensen @ 11:00 pm

Mobile/Notes/14-Jul-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

  • 2.0 Alpha 1 (tbd)

Major Topics for This Week

  • 2.0 Alpha Discussion
    • Blockers?
    • Sync Maemo and Android?

Front-end

  • Bug fix mode
    • Fixing reported bugs
    • Fixing breakage from move to e10s
  • Research mode
    • Tested some patches that remove tile canvas system
    • Exploring concepts related to planning tasks
  • Cleanup mode
    • Updating front-end code to current trunk style
    • Re-organizing some areas
  • Need to continue work on Planning 2.0 tasks
  • Summit session on “Understanding e10s for Add-on Developers” document

UX design

  • updates to a number of 2.0 details pages Mobile/Planning2.0
    • urlbarless designs presented at summit added to Mobile/Projects/AwesomeScreen2.0 – more coming this week
    • sketching out options for the VKB/search-engine-placement problem, adding to wiki today and tomorrow
    • continuing work on android theme Mobile/Projects/Android_Theme; next steps
      • awesomescreen
      • tools area
      • glyph revisions to add more color (no, seriously)
      • trying out the android “quick actions” design pattern (pop-up with grid of icons for actions)
  • posting “sharing data” summit talk to blog
  • started some “transitions” discussions at summit; to coninue
  • do we want to get anything to do with page-readability onto the 2.0 priorities list?

Maemo

Qt

Android

  • 19 blockers
  • multitouch zoom landed and is awesome
  • pause/resume regressed with e10s landings
  • protocol handlers still waiting for review
  • the latest version of the status bar notification patch, which includes all the comments, suggestions, and fixes, is ready for the last review

Electrolysis

  • Landed on m-c
  • Still finding and filing crash bugs
  • Toolkit components need to land
  • Places API changes need to land
    • stechz and mak should land today? (active)
  • Networking fixes need to land
    • SecurityInfo bug 536301 (need review and testing)
    • Redirects
    • Http Auth
    • App Cache
    • Suspend/resume (waiting on review)
    • Download Manager (active)

Layers

  • Where are we with Layers
    • Some code has landed
    • Need panning & shadow trees working before we can switch Fennec to true <browser>
  • Bugs to watch

General Platform

  • New manifest loading is breaking parts of Fennec
    • Prompts
    • Download dialog
    • Any other conflicting component overrides

Device API

Video

Camera

Plugins

  • InstallTrigger patch has a few test failures on mozilla-central due to bug 565389, so waiting on that

Performance

  • Investigating a possible bug with nsRefreshDriver running at 50Hz when it shouldn’t run at all (azakai)

Networking

Graphics

Startup

Layout

Content

Release Engineering

  • n900s should have fewer infrastructure problems
    • still not launching talos due to bug 575506 — anyone going to take this?
  • android, maemo5-gtk, maemo5-qt on try-as-branch (buildbot-0.8.0)
  • browser-chrome is close

QA

Manual

  • bugs filed on the Fennec product over the past week
  • Input will be mobile ready in the next 3-4 weeks
  • FORMFILL IS NOT OVER SIDEBARS. THANKS.
  • goals for upcoming week (in order of priorities):
    • Have Waverley start on nightly runs of trunk of n900s builds
    • Add assignments to the new features added
    • Start on adding testcases/testscripts to features landed (i.e. e10s and weave)

Automation

  • Android
    • getting¬†:bear setup for first runs on his system and tinderbox
    • investigating talos for android
  • browser-chrome
    • ¬†:adifire has preferences tests patch ready for review
    • need to enable browser-chrome, trouble with e10s ATM

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