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

  • FF 21.0b3 Desktop Shipped today
  • FF 21.0b3 Mobile is with QA
    • ETA for QA sign-off ?
      • Checked with :kbrosnan, looks like we are targeting Friday





  • Bug 837370 (js::types::TypeCompartment::addPendingRecompile) should be fixed in 21.0b3
  • Bug 852915 (mozilla::MediaDecoderReader::DecodeToFirstAudioData) is dropping and ended up being Win7 without SP1 only, we'll disable Windows Media Framework there, but one problem seems to be that our test boxes don't have SP1 as well.
    • bajaj to take an action to follow up with releng regarding when is the best time to do that & discuss on any issues we may face


  • Curiously, the EMPTY signature as well as the main D3D11 signatures dropped significantly in the last week, without any known reason.
  • Flash 11.7 might actually be better in hangs than 11.6
  • Overall crash rate of 20.0.1 has improved nicely to 1.7 crashes / 100 ADI, see
  • No changes in bug 851934 ( and bug 836263 (Crossrider).


  • Bug 752828 (database is locked) is down somewhat on 20 and 21, but that decrease has been scooped up by similar bugs 790922 and 862000.



  • Bug 812573 - hotfix to change update interval for existing pre-17 builds
    • [ashughes]: Assigned to myself, will try to have testing complete before EOD tomorrow

Verification Needed

  • Bug 830492 - Reduce total number of fsync() required by FHR
    • no way to reliably verify this, we'll need to monitor for regressive telemetry numbers as the change is adopted by Nightly/Aurora users. Can we set a checkpoint before the next merge to re-evaluate based on telemetry data that day? Who do we talk to to make analysis on telemetry data?
      • Comment in the bug to have a check point before we merge so ensure numbers look as expected




* [Urgent Request ] : 

Bug 862523 - Android: blocklist the STAGEFRIGHT feature on the following Hardware's: antares, endeavoru, harmony, picasso, picasso_e, ventana

    • Follow-up with :kbrosnan offline


  • hypothetically, if I had a friend who ... had some newer linux test hardware, and the tests/talos turn out to be as green & reliable as the old hardware, would we be able to switch to that for beta and release ?



Thunderbird (Tue)

Metrics (Thu)




Aurora Queries

Beta Queries