From MozillaWiki
< Mobile‎ | Notes
Jump to: navigation, search


  • Wednesdays - 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • #mobile for backchannel


[ ]

Major Topics for This Week

  • Spinning an RC!


  • Focus on 1.1
    • Bug list for possible bugs to fix for 1.1 (bugs)
    • Viewport patches have landed on 1.1
    • Web theme fixes have landed on 1.1
    • AMO/AddonRepository fix needs to land 1.1
  • Fennec 2.0
    • Worklist before merging mobile-e10s into mobile-browser
    • Support for new Add-on Manager is almost ready to land

UX design




  • nightly builds available
  • things are landing


General Platform

Geolocation Working Group


  • bas is reviewing layers gles patch (bug 562409)


  • implemented oggyuv container for source (input stream) and decoder
  • waiting for review from doublec (eta: next week)








Release Engineering

  • Android nightlies, rolled out nightly key
  • Bear has Tegras
  • bug 560844 broken l10n repacks -- has patch, needs testing
  • bug 557572, bug 557114 -- buildsymbols, crashreporter.
    • aki needs to turn maemo buildsymbols back on -- one line patch
    • ted needs to land crashreporter MOZILLA_OFFICIAL patch and land buildsymbols on branch
  • working towards Maemo5 release builders + repos; will need to run a test 1.1rc1 either way


  • Manual
    • notes:
    • goals for upcoming week:
      • release test 1.1 RC. here's our results wiki
      • verify and triage resolved bugs in fennec product
      • Get OS Intregation testcases up for Android
      • Start testing Android nightly builds
  • Automation (Android)
    • Current Status: Mochitests can be started, but we have a whole set of things that need to be done. More information here, but here are our next steps:
      • Finish the patch on bug 563860 – Joel and I have to work out a problem that patch has with how it figures out the xre-path to use to start httpd.js
      • Work out a better way for the & sutagent to agree on where data gets stored – I’m thinking once I get an SDCard for the board, this will get a bit easier
      • When we first made the sutAgents & the we assumed we would always be able to build our path to the installed application on the device. That isn’t true with Android. So, we need to figure out a way to not make “educated guesses” as to where Fennec gets installed.
      • We also can’t make any assumptions about what that executable name is: org.mozilla.fennec is the name, and it isn’t a directory. For instance there is no “org.mozilla.fennec/chrome”. So those shortcuts will have to be refactored.
      • We also need to actually install fennec automatically — still working that one out (I did this one by hand).
      • We need to land the Android SUTAgent in mozilla-central and build it from there (it’s been in our automation repo up to now). We have to do this because we dev sign the Fennec build and in order to have the sutAgent and Fennec be able to see each other’s data directories, then they need to have a shared ID and be signed with the same certificate. Bob and I have a patch for Fennec for this. And I’ll have a patch to add the Android agent to the tree along with a real makefile (I used a very hacked up makefile to make this work tonight).
      • Fennec did launch with the correct profile, but it did not launch with the correct URL. I had to hand-type the URL. I’ll file a bug on this tomorrow.