Firefox OS/2014 Foxtrot

From MozillaWiki
Jump to navigation Jump to search
Foxtrot -The Dance


Program Summary

The 2014 FxOS Foxtrot Program is open to Mozilla employees only (this may change depending on program requirements).

  • Goal: Increase quality and usability by gathering usage data from an internal audience audience
  • Dogfooders: Mozilla employess who will use the reference phone as their primay phone and report any problems or issues on a timely basis.

Foxtrot Lessons

Turnstep -The turn

  • How to sign up for Foxtrot emails
    • Go to https://mail.mozilla.org/listinfo/foxtrot
    • Fill out the subscription details and click subscribe.
    • An email will be sent to you asking for confirmation of your subscription request.
    • The list moderator will approve the subscritpion once the the confirmation has been received.
  • How to load nightly builds


Links

Etherpads:

Wikis:

TIMELINE

TIMELINE CHART
Name of pending task Likely ETA for completion Owner of the task
Getting Smoke tests on Flame device Start date unknown B2G QA - Tony
Current Perf stats Start date unknown Unknown

Random notes

  • Stable builds (of FxOS version release): QA verified, will have full ROM for download, and will have FOTA (firmware over-the-air) update.
  • Frequency could be one quarter or longer.
    • Weekly builds (of master): QA verified, will have full ROM for download, and will have FOTA update. Frequency could be one week or longer.
    • Nightly: will have full ROM for download only, NO FOTA update. Not QA verified. Question: how many nightly builds do we need to keep?
    • [n-1] build: Both stable and weekly builds above come from master (1.4 or above in this case). We should also provide the latest 1.3 (stable) build.
  • Though not included in original scope, we learned that there is voice asking for nightly FOTA builds. After discussing w/ vendor, the only feasible way while remaining cost effective is to have nightly FOTA builds w/ conditions listed below.
  • As T2M is leveraging TCL's FOTA infrastructure, FOTA builds may have 1~2 days of delay. That is, nightly builds could be 1 or 2 days old.
    • As keeping delta for nightly builds will be a management nightmare, providing full ROM FOTA seems to be the only feasible way. That is, no matter which nightly build you’re on, you’ll always get FOTA updated to the latest nightly build, w/ all user data wiped out. It’s basically the same as downloading the ROM build and flash the device.
  • With conditions above, we don’t see the clear benefit of having nightly FOTA. Therefore we propose to NOT have nightly FOTA, and stick to the proposal of the 4 bullets in the upper half of this mail. Thank you very much.