From MozillaWiki
Jump to: navigation, search

Channel Meeting Details

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.


marcia, lizzard, kmoir,elan, philipp, jcristau, milan, dveditz, selena, RyanVM, ritu, Jean, Tom

Previous Actions

Schedule Update

Current releases dashboard:

  • 52.4.0esr-build2 signed off and ready to push to mirrors tomorrow
  • More last minute 56 issues. Will build 56 again today (build 6)
    • Bug 1403063 - Disable VP8 HW decoder on windows 10 (should fix a top crash)
    • a sec issue
    • From Fri/Mon: Not letting certain screen reader users update to 56 (JAWS/e10s issues) till new JAWS update

Timing: Marketing is asking for 9AM Pacific on Thursday


Shield studies



[liz] Crashes from RC2 (56.0 build 4) release on monday:

  • Looks decent, not a lot of results, but OOM is on top, which means our top crashers from RC1 are probably fixed!


awsy rate: 2.23 (browser 1.17, content 1.06)



awsy rate: 0.97 (browser 0.74, content 0.23) telemetry (m+c-s) from saturday: 5.18 (week before: 5.33, this time last cycle: 4.14)

[philipp] both fixes for top crashes going into rc2 worked fine:

very early crash data for 57.0b3:


awsy rate: 0.86 (browser 0.62, content 0.24) telemetry (m+c-s) from saturday: 3.15 (week before: 2.90, this time last cycle: 2.53)



awsy rate: release 0.66 - beta 0.77 - nightly 3.37


  • Beta
    • Rate looks good. Some new bugs may need to be filed, but there are very few installs

Performance (Thu)

Aurora / Dev Edition





Aurora / Dev Edition


Action items




I'm not sure if this can all be handled in the channel meeting or if we should setup a separate meeting with releng/relman


   * re: marking what are the communication channels with Marketing. How can we know ahead of time for hard deadlines?

Questions for 56.0 release:

  • what build will be released - firefox 56.0 build5 now build6 apparently (from status of the 56 release: At risk email thread)
  • what's the expected timeframe for release? (e.g. Hour/minute/ if day is still unknown)
  • what's the hard-deadline (e.g. 6:00 AM PST like last time?) - from above 9am PT
  • what's the throttle rate we're aiming in the first place
  • do we throttle back to 0% after 24h or have a different approach this time - we need specifics
    • (from status of the 56 release: At risk email thread) Because we never had a chance to ship that to beta, we may want to throttle that release more conservatively in the first few hours, then ramp up the update rate quickly (within 6 hours) to the usual release day rate, 25%, until Friday.
  • liz - 10% for 4-6 hours, then up to 25%

future planning: also would be good to know release dates and times for the other five releases in flight RELEASE IN FLIGHT: fennec 56.0 build1 2017-09-22 - thursday same as desktop RELEASE IN FLIGHT: firefox 52.4.0esr build2 2017-09-18 - from above push to mirrors tomorrow RELEASE IN FLIGHT: fennec 57.0b3 build1 2017-09-26 - Tuesday


User Advocacy


  • (Callek) Crash Stats Symbols for DevEdition 57... [re: r-d e-mail]

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)