Release Management/Road to Mobile Beta 11

From MozillaWiki
Jump to: navigation, search

Android Market Testing

XUL Fennec (tablet) and Native Fennec (phone) up at the same time

Points of Contact: needed (catlee/coop/tchung?)
State of feature on 1/31:

include any work you're still hoping to land during beta

Blocking bugs:
  • bug 719560 – Can't publish split native and xul builds under the same product on android market
  • bug 721551 – Need split builds for Fennec that serve XUL Fennec for tablets and native Fennec for phones
Blocking work:

untracked in Bugzilla

Estimated landing date on m-c: n/a
Estimated uplift date to Aurora: n/a
Planned testing:

engineering, QA, test audiences

  • RelEng to upload private XUL build
  • QA to install private XUL on tablets and phones
  • RelEng to upload so that the XUL build is delivered for tablets, and the native builds for phones
  • QA to update tablets and phones from the market, ensure they get the correct products
  • RelEng to upload native build for both tablets and phones
  • QA to ensure all devices get the same APK
Estimated testing completion date:
Other notes:


multiple single-locale APKs

Points of Contact: Axel and Aki, Martijn (QA)
State of feature on 1/31:

include any work you're still hoping to land during beta

Hopefully built on nightlies, tested for functionality + AUS updates
Blocking bugs:
  • bug 702302
  • bug 698425
  • bug 705214 - update snippets, if we need these single locale apks to update via AUS. ETA 1/20 ?
  • bug 659544 - partner repacks, if we need those single locale apks to update via AUS. ETA 1/27
  • bug 717522 - android-xul not repacking
  • bug 714553 - may be causing the android-xul repack issues
Blocking work:

untracked in Bugzilla

Estimated landing date on m-c:
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

  • Engineering produces private builds of the locales
  • RelEng uploads the private builds for each locale
  • QA tests that the correct APK is delivered for locales
  • Need to add AUS test coverage for betas/release builds
    • Website testing too
  • Test multilocale -> single locale updates
  • Light partner repack testing (at least a spot check, as these will go into the market)
  • Multilocale testing if we're going back into the Amazon market
Estimated testing completion date:
Other notes:



Profile Data Migration

Points of Contact:

gcp, kbrsonan

State of feature on 1/31:

include any work you're still hoping to land during beta

Blocking bugs:
Blocking work:

untracked in Bugzilla

  • Blocking work goes here
Estimated landing date on m-c:
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

Estimated testing completion date:
Other notes:




L10N

engineering work

Points of Contact: Doug and Axel
State of feature on 1/31:

include any work you're still hoping to land during beta

Blocking bugs:
Blocking work:

untracked in Bugzilla

  • String freeze, blocked on Sync
Estimated landing date on m-c:
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

Estimated testing completion date:
Other notes:


string translation coverage

Points of Contact: Axel
State of feature on 1/31:

include any work you're still hoping to land during beta

No estimates until we're string frozen for a bit.
Blocking bugs:
Blocking work:

untracked in Bugzilla

String freeze

Estimated landing date on m-c:
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

Estimated testing completion date:
Other notes:



Sync

core, setup, bookmarks, and history

Points of Contact: Ally
State of feature on 1/31:

include any work you're still hoping to land during beta

Setup:

  • Done:
    • J-PAKE and fallback setup
    • Bidirectional pairing
  • Aiming to land before beta uplift:
  • Will not land:
    • Editing/correcting credentials.
    • Notification for incorrect credentials.

Core:

  • Done:
    • Enough to deliver something that looks like bidirectional syncing.
  • Aiming to land before beta uplift:
    • Likely to get clients engine, backoff handling, and basic reset handling done.
  • Will not land:
    • A complete and thorough Sync implementation.


Bookmarks:

  • Done:
    • Basic syncing of regular bookmarks and folders.
  • Aiming to land before beta uplift:
    • Extensive improvements for reliability (bug 718238).
  • Cannot implement:
    • Queries, microsummaries, livemarks…
  • Will not land:
    • Favicon sync.

History:

  • Done:
    • Pretty much complete. Not tested with history pruning in effect.

During beta:

  • Improvements and fixes only. No major features planned to land.
Blocking bugs:
  • bug 718493 — tracking bug for Aurora uplift in late Jan. Not committing to any other work.
Blocking work:

untracked in Bugzilla

Estimated landing date on m-c:

1/13

Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

  • We plan to request testing from the MTD audience once landed on beta, as they've been excited to start testing.
  • Services QA and Mobile QA are performing regular testing of builds.
Estimated testing completion date:
Other notes:


passwords

Points of Contact: Ally
State of feature on 1/31:

include any work you're still hoping to land during beta

Some basic work on passwords engine done, untested and not integrated.

Blocked on Fennec content provider for passwords (bug 704682). If that gets done, integrated, and works, we might get bug 709385 done by the end of January. Otherwise it'll get done when it gets done.

No Sync-side work done on tabs (bug 709403). Blocked on design, spec, and implementation of Fennec tab interfaces (bug 715644). Nothing will land this quarter. It has been descoped from 11.

Blocking bugs:
Blocking work:
Estimated landing date on m-c: When done.
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

  • Services QA
  • MTD
Estimated testing completion date:
Other notes:



AMO Support

Points of Contact: Gregory Koberger
State of feature on 1/31:

include any work you're still hoping to land during beta

Blocking bugs:
Blocking work:

Requires action outside of the trains

  • Fligtar to Confirm /android is the best name space
  • Fligtar to confirm w/ WebDev on timeline
  • Fligtar to drive hardcoding of version # in the UA string
Estimated landing date on m-c:
Estimated uplift date to Aurora:
Planned testing:

engineering, QA, test audiences

  • We need Fligtar's team to complete due testing process on the webdev side
  • Fennec Native QA needs to make sure all AMO support in the app correctly links to the AMO page
  • Communication to Add-Ons Devs should test AMO website and MTD testing audience should test support in fennec native app + add-ons themselves
Estimated testing completion date:
Other notes:
Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/Road_to_Mobile_Beta_11&oldid=391088"