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# 99951 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99951 (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.


lmandel, sylvestre, ritu, lizzard, elan, bsmedberg, mknous, avaughn, philipp, jst, milan, dveditz, blassey, ryanvm, mbest

Previous Actions

Schedule Update

  • fx 47 desktop beta8 is live
  • fx 47.0b8 mobile later (will upload to playstore shortly)




Overall rate: 1.82 (orange) - browser 1.24, content 0.59


Overall rate: 1.19 (orange) - browser 1.03, content 0.16


Overall rate: 1.00 (orange) startup crashes: 0.13, shutdownhangs 0.2



Release Health report

  • Beta: 4 blockers, 19 new regressions
  • Aurora: 1 blocker, 110 new regressions
  • Nightly: 2 blockers, 18 new regressions
  • All blocking bugs are assigned and WIP.

Performance (Thu)

Aurora / Dev Edition





Aurora / Dev Edition


Action items





User Advocacy


System add-on updates

(bsmedberg) Intend to convert the plugin blocking experiment to enabled by default and ship it with Fx47. We'll be shipping the "conservative" list for now. The conservative blocking scheme blocked about 0.5% of all plugin loads. It reduces the plugin crash rate by 10±4%. It reduces the plugin hang rate by 4±2%. It may have decreased Firefox pageload time by 5%, but the statistical confidence in that number is very low. \o/ should be in 47 release notes??

    • yes, once we have the blog post
    • Potential risk mitigation if we go down this path for Fx47
      • We can turn the pref off (hotfix'able)
      • We can unblock specific plugins from Shavar server (does not need hotfix or dot release)

[lmandel] We've talked (perhaps more than talked) about transitioning the hotfix to a System Add-on. Who owns this and what are the next steps to make this happen?

    • Any drawbacks?
    • Will this address some of the issues that we have with hotfixes? hotfixes are not installed one after the one (only the last one), no confidence that users updated, the property has to be renamed, etc
    • Benjamin owns it and this is planned for Q3 2016
  • Hello 1.3.2 to ship-to-release-Fx46 staged rollout at 10% on May 23rd.
    • After 48 hrs, if all goes well, the updates will be at 100%

Telemetry Experiments

  • Beta47
    • Plugin content blocking (Bug 1248813)
      • Start date: 47.0b2 ; End date: 47.0b8 (gtb)
      • This has stopped
    • E10s turned on for 20% beta population (Bug ???)
      • Start date: 47.0b1 ; End date: 47.0b6
      • We decided to run this experiment for entire Beta47 cycle (as an exception)!
      • No uplift for e10s changes

Additionall Priv/Sec Work Targeting 49=

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)