From MozillaWiki
Jump to: navigation, search

Channel Meeting Details

  • Tuesdays at 10am PDT, and Thursday at 2:00pm PDT
  • Mountain View Offices: Warp Core Conference Room
  • San Francisco Office: SFO-7I Independent (Tues), Noise Pop (Thurs)
  • #planning for backchannel

Video/Teleconference Details - NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 99951 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99951 (US)
  • Vidyo Room: Release Coordination
  • Vidyo Guest URL
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.

Previous Actions

Schedule Update

  • FF21.0b4 for Desktop/Mobile shipped


  • Nothing new to report.



  • (js::RemapWrapper) remains the main concern, a possible bandaid fix is up now.
  • KaiRo commented in the dev-planning "Using a pre-processing flag to auto-disable features in later Beta versions" thread how the low ADI esp. on Aurora but also on Beta lead us to make compromises and end up testing on higher channels than we'd like to.




  • A number of stagefright blocklist patches landed for 21.0b4, one or two additional ones might be needed to improve even further.



Verification Needed




  • 856445 – Startup crash on LG Optimus Black (LG P970)


Nothing today



We are watching closely for feedback around Bug 865701 after Beta 4 releases, hopefully will get auser willing to work with us if needed

Thunderbird (Tue)

Metrics (Thu)


a) Since the data that we have is very early data with practically no users we push Fx 21 Beta 4 today as planned. b) Spin another beta with the same changeset and keep an eye on the crash-volume and do an early push if we are sure it helped by Monday ? c) Spin another beta and reconsider adding a patch with padding in this particular scenario to see if it helps ? d) Any other ideas that may be helpful here to mitigate the problem ?

  • & (Radeon 6310)
    • We should already build a beta for Desktop with the same changeset and put it on ftp
      • Question here for :bsmedberg : making sure taking the same chageset is ok here in the hope of avoiding this crasher or would it matter if we took a newer changeset ?
    • Any other speculative fixes(padding) that we could land for this particular top-crasher ?
    • If the crash volume spikes unexpectedly in Beta 4 as early data suggests
      • Check the early crash-data corresponding to the new beta and if it helped push it out early or verify it with STR if we were able to find one
  • For final Fx21RC build :
  • Like we did in FX20, we should go-to-build right after our final beta & put it on ftp & rely on the crash-data to see any unusual spike this build may have for the Radeon-crasher
    • If so, immediately spin a new RC with same changeset ...
  • (next actions) :benjamin will have more data shortly which may help QA to assemble machines with those configuration and try reproduce
  • try to identify particular OEM builds that could help QA
  • device a plan for the RC build, mostly comparing pre crash data from ftp to the new build.
    • this will involve comparing the data for every beta for the time its been on ftp vs post release to see if we can co-relate and increase confidence



Aurora Queries

Beta Queries