B2G release drivers

January 2014

• Jan 13, 2014
• AI from last week:
  • Tarako Gecko features - AI: Karen (delegated to bwalker)
  • notes from bwalker as requested by Karen:
  • I took some snapshots of the memory consumption for Facebook, Twitter, YouTube, Cut the Rope, and Firefox Marketplace using the tools/get_about_memory.py tool
  • Steven Yang says to focus on the explicit memory allocations for each app.
  • My initial numbers are Facebook: 32MB; Marketplace 21MB; Cut the Rope 44MB; YouTube 19MB; Twitter 22MB.
  • In the b2g 1.2 build I was testing, total of explicit allocations for the always running apps in Firefox OS appears to be about 80-90MB
  • CONCLUSION: some apps might run, if their peak memory allocation is no bigger than their average allocation (bad assumption)
  • CAVEAT: need a lot more testing to try to find peak memory allocation
  • RECOMMENDATION: assume that apps don't run on 128MB phone unless proven otherwise; create a super-restricted view of Marketplace showing only a handful of approved apps.

• Agenda:
  • [jsmith] MWC Demos
  • QA Need - Access to new ZTE & TCL devices
  • Where are we with MWC?
  • Candice collecting demos from teams
  • Link for the same:
  • 2 levels of demo -
  • 1) floor level demo - 1.3 builds - LG 1.1/ Huawei 1.1/ TCL/ ZTE - QA to run sanity and test scripts
  • Devices: ZTE/ TCL - end of Jan - 40/60 pieces - coming to Taipei or China to Barcelona
  • Would it be possible for the flash team to get a couple of devices so that they can go through flashing the devices?
  • 2) Foxden - limited audience - 1.4 version - device:
  • [pdol] 1.3 MWC build plan
  • device/demo tracking: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AkNv3O9ZjM0ZdEZ3ZUQxUWpDQm5MU2daQm5xMW9TYmc&usp=sharing#gid=1
  • [jsmith] Risky Tarako Landings - Need Separate Branch
  • Bugs not recommended for 1.3 uplift or POVB http://goo.gl/E6QcrA
  • Tarako branch next week (after landing QC CS blockers) for both Gecko/Gaia (similar to 1.2F/1.1HD)
  • Fugu is 1.3 - http://mzl.la/1ayGv8c (45 bugs now) - Joe and Steven to figure this out

• [jsmith] 1.3 v/s 1.4 resourcing
  • 7 items slated for 1.4
  • 1.3 blockers status (137 open bugs today) -- plans/status to converging
  • Are we re-triaging this list for 'real blockers'?
  • http://goo.gl/Y64PU0 - (I saw 136 now - there's 138, as 2 are security bugs)
  • Provide a read out end of week: Preeti

• [jsmith] Update on reference device
  • One device tomorrow (EVT), and will have review call w/ T2M later this week
  • On track MWC device - Jan 27 - 150
  • 2000 phones end of March

• [jsmith] 1.4 Release Process Changes from 1.3 (Bug Triage, Release Length)
  • 2x 12 week release cycles
  • Within 24 weeks - call it cycles
  • Feedback from QC - no CS every release
  • Needs additional discipline irrespective of QC CS - Engineering responsibility
  • Send out the schedule to the rest of the team
  • Next steps:
  • Scheduling - Preeti
  • Scoping of features on Moz plate

• Pike's notes for l10n and 1.4, not attending due to timezones:
  • Ask on behalf of l10n contributors is similar to the core engineers:
  • knowable item of work
  • no competing work among several targets at the same time
  • The challenge comes due to the time difference between the engineering and the localization tasks.

L10n-related tasks that should find their place and time on the schedule (for ex. reasonable l10n freeze date), in chronological order:

• • • l10n experts community follows core developers as they finalize their work and give input on both a PR and post-landing level, just within a few days
    • l10n community at scale follows the development, on a given contribution path and a given item of work
    • QA resources test, this is a point where moco steps up to cover for lack of QA talent in the communities
    • Fixing the bugs found during the QA cycle, dozens per locale in the past
    • [delphine] l10n schedule was incorrect on the v1.3 fxos schedule. Correct time-line has been updated today: https://docs.google.com/spreadsheet/ccc?key=0Ar-YjAa9FrqLdHd4NGlnQkpYMmtoWWFzaTRLdHFYZUE&usp=sharing#gid=0
    • Shows soft l10n freeze/testing is Jan 17th, this Thursday. Typically lasts 2 weeks. Issues:
    • No major outreach to communities yet, translations still need to be completed: https://l10n.mozilla.org/shipping/dashboard?tree=gaia-v1_3
    • we're still waiting to hear about possible new locales for 1.3: India and Africa?
    • Testing ressources available? which leads to main question: Can we be more flexible in l10n schedule for 1.3? Can we start testing later? No sense in starting Thursday, nor next Monday. Pushing back one week?
  • TCL - mid Feb IOT - Telefonica
  • ZTE - 1/22/14 - 1st round of IOT.

• Jan 6, 2014

• Joe (unable to join from EU timezone): 8x10 modem memory usage: We need to continue pursuing with QC on 8x10 modem memory optimization (also with requests to QC from OEMs). Email from mvines before the holiday: "We are currently projecting that 175MB of physical RAM will be available to apps userspace and dynamic kernel allocations by 8x10 CS. This is a reduction of about 10-15MB from 7x27a unfortunately. Optimizations are in the works for this gap but they will not be ready for the end of January CS release. Depending on OEM demand and launch timing of 256MB SKUs, it’s possible (but not committed at this time) that we would have a post-CS release to bring in these optimizations."

• [jsmith] Tarako App Content Requirements
  • Pre installed apps - high memory consumption
  • What apps need to work v/s not?
  • Spreadtrum requirements were not app specific
  • https://wiki.mozilla.org/FirefoxOS/Tarako#Bugs_querying_.5Btarako.5D_in_whiteboard
  • Gecko features which are memory consuming - eg.,SkiaGL -
  • Karen ask Bill Walker for minimum app rqmts/impacts

• [jsmith] Mozilla RIL requirements for RIL features in 1.3+
  • Code compatibility with QC RIL
  • Need reference development given we will not have a QC RIL for reference
  • Testing will be impacted
  • Sandip/ Ravi to talkt to QC

• [jsmith] Accountability in Release Process to Prevent Death by Papercuts Problem
  • Regressions/ low priority bugs/ papercuts - what next
  • no action as yet
  • Product team being involved with planning and prioritizing for the respective teams
  • Meta bug per functional team to be created.
  • 1.3 CS should be P1: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocked%3A942267&list_id=9102293
  • Jan 10th to land QC CS bugs
  • Jan 15th is QC date for CS build

• Madai Status: Top level requirements ownership clarified (Except some LG requests to be confirmed if must-have)
  • Request owners to open bugs and start tracking development for each feature from there [Wayne to request owners]
  • UX/Product workshop happening in Taipei on Jan 22
  • Network workshop happening in Taipei on Jan 20-21
  • Moz needs to own IPV6 - Ken from Taipei to look at it
  • Worth noting that QC owns much of the IPV6 implementation and has committed to finishing the platform work in 1.4
  • Resourcing for UX for camera for LG - Jaime looking at the same
  • LG requests Moz to provide visual assets/interaction designs by end of Jan otherwise they would re-use the camera UX from their android product