Mobile/StatusMeetings/02-24-2011

From MozillaWiki
Jump to: navigation, search

« previous week | index | next week »

Agenda

  • AIs from last meeting
    • All: Edit B5 Release Notes
    • Stuart / Thomas: Create 2011 and beyond Roadmaps for Firefox for mobile and for Firefox Home
    • Stuart / Thomas: Encourage internal testers to use Beta 5
  • ACTION ITEMS
  • Beta 5: User Feedback Update
    • as of 2/23/2011: 661023 downloads, 330032 active (49.9%), ratings (5/4/3/2/1) 2123 1401 1434 1032 1365 = 3.25 stars average (slight increase)
    • ratings from past 24 hours: 157/99/71/34/32 = 3.8 stars average!
  • Beta 5: launched Feb 23!

2.0

2.0 planning page

Localization

Filed Bug 634679 to address some potential issues with nightly testing and using lang packs.

Dashboard updates: https://l10n-stage-sj.mozilla.org/dashboard/?tree=fennec_mc

Seth continues to post these notes and the schedule to the l10n community.

Release Engineering

  • Progress tegra talos testing (18 -> 1 over the long weekend)
  • Two multi-hour tree closures, working with IT to avoid until after Fennec4.0
  • FYI: branching decisions coming soon for mozilla-central.
    • Anything you need landed before branching?

QA

Issues to Know

Marketing & PR

  • Streamling release process
  • Spark campaign continue 
  • SXSW Mobile Event 3/11-3/14
  • Working with jgrlicky and jslater to update Firefox.com/m page and Firefox.com/mobile/download page to reflect final release(QR codes and over-the-air)

Feedback Summary

Top Comments from Android Market:

1. No Flash
2. Faster
3. Excessive memory consumption

Issue SUMO Input Buglink
No Flash support New 21611 Dn 16
No copy/paste support
5 {{bug|585875}}, {{bug|611741}}
How to disable popup blocker New 16 -

Reformating text on zoom 4
Firefox for iPad/iPhone? New 5421 Dn

Firefox for Symbian? New 32 Up

Firefox for Blackberry? New 18 -

Problems with Marketplace New 75 Dn

Support

  • Feedback wanted/needed on Mobile Support Strategy in 2011 (pdf). At a high level, these are the main focus areas:
    1. Create clear and intuitive paths to support.
    2. Optimize the entire website experience for small screens.
    3. Expand and optimize the self-service support content.
    4. Provide regular reports with support insights to product, engineering and QA teams.
    5. Grow and strengthen our community to include contributors specializing in mobile support.
    6. Dedicate a full-time resource to drive and expand the mobile support efforts on SUMO.
  • The new mobile layouts for SUMO are in progress right now - check them out by pointing Fennec to http://support.allizom.org/mobile