From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

Channel Meeting Details

Video/Teleconference Details - NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 9951 (US/INTL)
  • 1-800-707-2533 (pin 2) Conf# 9951 (US)
  • Vidyo Room: ReleaseCoordination
  • 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.


nicole, julien, Ritu, Tom, elan, RyanVM, milan, philipp, dveditz, callek

Previous Actions

Schedule Update

Current releases dashboard:

  • 56.0 mobile shipped last Thurs at 10%, and is now at 99% update rate on the Play Store
  • 56.0 desktop: shipped last Thurs for 24 hours
    • crash rate good
    • delay yesterday over major functional issue with addon affecting ~1% of users.
    • Not ready to re-enable updates at 100% just yet
    • New news. We have a bug in kinto that means our new blocklist updates aren't working

  • we forgot to ship devedition 57.0b4 on friday (kmoir apologizes for this, I blame my sleep deprived state on Friday)
  • 57.0b5 beta and devedition are out
    • devedition was supposed to get a WNP, but it's only shown to those who haven't yet updated to 57.0bX
    • Suggest sending email to r-d about WNP not being available to 57.b users and only to users updating from DevEd < 57 to 57b


Shield studies



awsy rate: 2.75 (browser 1.20, content 1.55)



awsy rate 1.14 (browser 0.66, content 0.48)

[philipp] content crash rate higher in 57.0b - would be interesting to know how this corresponds to e10s usage

  • Romain/Pdol will reply


fixes in b5:


awsy rate: 0.84 (browser 0.61, content 0.24)

[philipp] 56.0


awsy rate: release 0.65 - beta 0.92 - nightly 1.71


Performance (Thu)

Aurora / Dev Edition





Aurora / Dev Edition


Action items





User Advocacy


  • Policy for DevEd shipping
    • Except for beta1 sign off which will be gated on a formal QE/relman sign off, releng team should push both the Desktop (vanilla beta) build to beta channel and the corresponding DevEd build to the appropriate update channel at the same time.
    • This should be the process starting from beta2 build until before RC builds.
  • About Devedition, we would like to do the same as 57 for 58/59 to gather more data.
    • The adv of this is we can go to 100% beta population sooner
    • We need to confirm Code freeze date for 58/59 as that might have an impact to engg.
    • the milestones doc was very useful, we should do that again to provide clarity to everyone

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)