Fennec/NativeUI/Showcase1-25

  • To refresh on the list of Features and their priority, click here.
  • To refresh on the plan of record per Toronto's offsite, click here.
  • To see baseline vs. current reality, click here: here

ADU update

  • Aurora - 1,076, +12% from last week
  • Nightly - 1,172 +2.5% from last week
  • Beta - 25,940 +2.5% from last week

Schedule

Q4

  • Dec 2011: Feature Complete

Q1

  • Jan 16 2012: String Freeze ==> Jan 30th (lock-step with cutover)
  • Jan 16 2012: First Run Walk-Through ==> needs to be reset; pending profile migration which is getting closer
  • Jan 30 2012: Beta Cutover & Beta Declare
  • Feb 27 2012: Public Announcement at Mobile World Congress
  • March 30 2012: Final Release

Beta Readiness

Features

  • Split-APK
    • Status: Waiting for the fix for bug 719560
    • Requires: QA testing on tablets/phones once posted
    • Fallback options: Push XUL to all for the time being, only push to tablets, hold off on pushing altogether
  • Profile migration
    • Status: Waiting on the fix for bug 713283
    • Requires: QA test plan and verification (kbrosnan: test cases are complete & ready to go)
  • L10N
    • Required for String Freeze for Fx11 (Jan 30th): [bug list here]

Marketing/PR

    • Johnath's blog post on trains: will be pushed today
    • Press release for beta being in progress

(P0) Stability and Performance

Crashes

  • http://bit.ly/tr4pBc - currently we have 10 top crashes
  • 12.0a1 - stats for yesterday - 526 ADU with 31.34 crashes/100 ADU
  • top crash #1 - bug 718765 is fixed but still showing up in high volume with people running builds before Jan 19th.
  • top crash #2 - bug 719872 is in progress and a fix should be coming soon.
  • These 2 crashes account for just over 50% of the crashes.
  • We have pulled out java signatures and logged bugs in an attempt to make the top crash list more actionable
    • % of crashes that occur within .5s of startup and compare to XUL over nightly/aurora (smooney can help)
    • Devices that are crashing on launch (0?)
    • How many crashes in the top X has not exhausted QA/engineering possibilities for reproduction
    • Explanation of aurora/nightly population, affect on our testing

https://metrics.mozilla.com/pentaho/content/pentaho-cdf/RenderHTML?solution=metrics&path=blocklist_fennec/blocklist_fennec0&dashboard=template.html&template=new-metrics&title=Fennec%20Usage

    • Explanation of apples vs oranges
    • Web content crashes didn't appear in XUL
    • We're doing more in Java, so there will be more Java crashes

Performance and Responsiveness

Goals Related to Competitive Browsers

  • Raw Start: To be within 200MS of the Stock Browser for

[See Video]

  • Warm Start with Page Load: We need to be within an acceptable range with Stock and faster than Opera

[See Video]

  • Scrolling Panning, Zooming, and Frame Rate should meet or exceed customer expectations when compared to other mobile browsers

[See Video]

  • XUL Beta vs. Java: What will users see?

[See Video]

  • XUL Beta vs. Java on Droid Pro

[See Video]

Compared to XUL: Where are we Better, Where are we worse?

  • Better: We use less memory, we now have async panning & zooming, faster frame rate, sync now runs in the background,
  • Worse: Checkerboarding, Closing tabs, Loading multiple pages at the same time, possibly tab restore
  • Worse: What are we doing about it and when?

Checkerboarding and responsiveness changes in flight, targeted to land prior to beta:

Other Top Issues and Their Status

Sync

Website Compatibility

(Two-pronged approach)

MTD Update

MTD feedback in order of frequency:

  • "Feeling zippier"
  • Sync <--- people still want sync
  • Remaining checkerboarding
  • Localizations
  • Unzooming during page load
  • Frame rate when scrolling
  • Top sites still don't work
  • Flash on ICS