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.


lmandel, elan, sylvestre, jst, dougt, rail, roland, kairo, milan, philipp, lizzard

Previous Actions

Schedule Update

  • beta 9 updates disabled
  • 42 RC desktop
    • Not fun
      • A sec fix caused some regressions - backout
      • an async plugin init change which caused a top / startup crash - backout + async plugin init = off (missed beta 9)
  • 42 beta 10 mobile
    • uploaded
    • x86 random crash not fully fixed
  • started esr 38.4.0 build this morning. (liz)



Aurora / Dev Edition

  • Overall rate: 2.5 (target: <1.5) - browser: 1.4, content: 1.1 - red, up from last week, huge spike over weekend
  • content has been going down, probably because the Telemetry Experiment disables e10s for a number of people.
  • bug 1218395 (nvd3d9wrap.dll) is really high
  • bug 1218128 / bug 1218473 is present here as well, see discussion in beta section
  • there's a js::jit::CodeGenerator::generateBody signature that is #1 now and still needs a bug filed
  • bug 1218266 is crashes that are caused by the Telemetry Experiment running for e10s.


  • Overall rate: 1.5 - red, up from last week, huge spike over the weekend
  • top issue by far is startup crash bug 1218128 / bug 1218473, caused/triggered by bug 1213567, we did a backout for RC to hopefully fix this.
    • this would normally revert to having the crashes reported in bug 1213567 but we hope disabling async plugin init (bug 1216665) will mitigate this in RC.
    • Discussion on how to use the release channel to test feature
      • In some cases, we don't get enough information with the beta channel (ex: OMTC, async plugin init, various graphic driver issues), future: e10s
      • how to improve the quality
      • Only happened when 42 reached beta (e10s was on on nightly/aurora)
      • Diversify the beta population to match the release


  • Overall rate: 0.9 - green
  • looks like the workaround for Win10 crash bug 1189940 worked on beta 42 \o/


  • beta crash rate is up and firmly red at 4.0, double of the target.
  • bug 1207642 fixed at least some part of random hex crashes, unclear how much it influences the overall rates.
  • bug 1215950 is the clear #1 signature, probably to blame for beta crash rate increase, fix in b10
  • bug 1201081 is #2 and also has a fix in b10

Performance (Thu)

Aurora / Dev Edition





Aurora / Dev Edition


  • looks like we don't have RC on beta-cdntest yet, waiting for that so we can run update tests


Action items





User Advocacy


  • e10s
    • what we should do?
    • what kind of data we should gather?
    • how we can deploy to a % of users?
  • Shipping on purpose dot release
    • 1 week after, 3 weeks after?
    • how to do this and not burn us all out? (relman, releng, sheriffs, qa)
    • Update the mechanism
    • make it so the UI tours don't come up again for "minor" or planned dot releases

Special Topics

Discussion of platform quality.

Aurora/Beta Feature Review

Main concern with 43 right now is SHA-1 deprecation issues. We need more work for win xp, 7, vista users to be able to update from 43 onwards. Over 6 M users could be stuck.

e10s opt-in for 43.0 Beta:

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)