Fennec/NativeUI/Showcase2-15

From MozillaWiki
Jump to: navigation, search
  • 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,268 (+4.2%)
  • Nightly - 1,310 (+9.8%)
  • Beta - 26,488 (-2.9%)

Schedule

To see who is attending the showcase

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 *==> merge happened but we are day-for day slip until we have maple landed in m-c*
  • Feb 27 2012: Public Announcement at Mobile World Congress
  • March 30 2012: Final Release ==> *this is changing; we are re-setting the schedule and are working card to be as close to Q1 as possible*

Beta Readiness

  • This is bottom line: we are gated on open gl layers landing in m-c and having QA and stakeholders sign off on performance stability characteristics. We are day-for-day slip
  • We want to ship the code to beta as soon as it is ready
  • We are 95% certain this will happen within fx13
  • We can move off of the trains if needed; we won't gate on them. This means we don't think it will be as far out as June 5th and that the end of April is likely
  • This effort is the long-pole, though Sync functionality is also a critical piece of beta criteria

Release Management

Ship strategy:

  • Plan to ship XUL Fennec 11 for beta 3, and continue shipping off of mozilla-beta until Native Fennec is ready for beta
    • This gets us more testing of the latest core gecko changes on mobile until Native is ready
    • This also gets us testing of security fixes prior to XUL releases
  • Plan to ship XUL Fennec to release off of the ESR10 branch until Native Fennec is ready for release, starting with our 3/13 date
    • This is security fixes only, so internal QAing should be sufficient.
    • In the unlikely case we need to chemspill for mobile, so be it. Thankfully we leverage the Android Market instead of our own updater so our update path won't ever be borked.

Open work:

  • Aki to stand up ESR builds before our 3/2 go-to-build
  • We're working with the Soccorro team to get the ESR into crash-stats for Mobile

Open Question: What should we do about release notes? And other product considerations.

Demos

What is happening for MWC?

  • To see Demo Content: http://paulrouget.com/mwc-demos/
  • We are showing XUL for tablets: UX is awesome and we have full sync functionality. We are also targeting canvas demos
  • We are *only* showing Native on phones; we are currently targeting nightly. Maple branch being ready will be a nice surprise
  • Paul Rouget is reving the content by 12:00 PST tomorrow; QA will be poised to test
  • Burn Down List: http://bit.ly/wzthK4
  • Triage for Maple is happening @ 2 PM to determine the P1's for mwc. Focus is on general functionality and web readiness; possible readiness for canvas demos for phones.

Other Top Issues and Their Status

Sync

  • They are uplifted to Aurora: plan of record is to go to beta with history, bookmarks passwords, tabs- possibly form fill
  • We need to get to the bottom of awesome bar performance after sync
  • Password content provider bug 704682
  • Need to talk about additional data types
    • Forms (gated on wes getting passwords done, and then form API)
    • Tabs (no UX, no one assigned to content provider/data store, highly at risk)

Font Inflation

  • Need to understand latest state of font inflation, what would block beta?

UX & UI

Of our UX list for beta: this needs to be updated; need to circle back with Madhava. If we ship what is in Fx13 (m-c) we may have opportunities to make high value UI changes.

  • Done
    • Get the in-browser Sync UI pieces in, so people can find and set up sync bug 708414, bug 716906
    • Get the tab menu not covering the whole screen -- may seem minor, but I want people to get the right idea of how it works as of beta - bug 712526
  • Improved
    • aweseomescreen - slow top sites list coming in
    • tab menu - opening a tab, switching tabs, deleting tabs
    • Fix the p1/p2 font inflation bugs -- we want this to be as right as possible for beta; bug 706193, bug 706198
      • mobile sites exception is done - is it in nightlies/aurora?
    • Some thumbnail tweaks around differences in tab menu / start page, scaling where we shouldn't be (bug 721032)
  • Still to be fixed
    • Cut down the amount of checkerboarding - bug 716581
    • Get frecency / top sites as right as we can: bug 704977
    • Handful of startup weirdness bugs: tracked in bug 721008
    • [new] Overwhelming flat list of desktop bookmarks bug 716918

Website Compatibility

(Two-pronged approach)

MTD Update

  • Currently in a holding pattern (MTD has turned into an engagement channel) until we've got something new for them to test (OpenGL Layers on Aurora)
  • We have 104 new people in the ready to help test (with device) on our sign-up sheet