Firefox/Channels/Meetings/2016-05-24

Channel Meeting Details

• Tuesdays and Thursdays at 10am Pacific Time
• irc.mozilla.org #planning for backchannel
• Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

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

Attendees

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)

• Potential hotfix to disable brotli on 45
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1273547
  • benjamin suggests using a system addon with a default pref since it would then go away at the next update (unlike hotfixes)
  • felipe could help

Add-ons

Stability

Aurora

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

Beta

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

• various signatures regarding d3d11 media playback are 2.9% on 47.0b7: https://crash-stats.mozilla.com/search/?product=Firefox&process_type=browser&proto_signature=~D3D11DXVA2Manager&proto_signature=~CDecodeContext&version=47.0b7&_facets=signature&_facets=platform_pretty_version
  • landing of https://bugzilla.mozilla.org/show_bug.cgi?id=1273691 in beta 8 should address a number of those
• amd gfx crash with signature TppTimerpExecuteCallback https://bugzilla.mozilla.org/show_bug.cgi?id=1270686 is 1.05% and blocking 47
  • people are working on a patch to get more diagnostics about this issue
• new crash signature nsPresArena::Allocate https://bugzilla.mozilla.org/show_bug.cgi?id=1275239 is 0.5%
  • seems to be introduced by the update of a particular addon and only affect 47.0b builds so far - maybe blocklist?
• nsPerformanceGroup::Dispose https://bugzilla.mozilla.org/show_bug.cgi?id=1261702 is 0.5% and needs an owner

Release

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

• blocklisting for trend micro crash https://bugzilla.mozilla.org/show_bug.cgi?id=1196899 has gone into effect (all variants are still amounting to 1.3% of crashes in 46.0.1) yay thanks!

Nightly

• Project Uptime is keeping up with logging new crashes - https://wiki.mozilla.org/Platform/Uptime/Logs#2016-05-24_-_ting
  • New crash sig - https://bugzilla.mozilla.org/show_bug.cgi?id=1275030 - Perma startup crash when using the skia content backend on Windows 7 - most likely all from mchang while bisecting/testing

Mobile

• https://bugzilla.mozilla.org/show_bug.cgi?id=1274488 - Android Nightly builds broken because Mercurial 3.1.2 is used

Release Health report

https://mozilla.github.io/releasehealth/?channel=beta

• 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

Beta

Release

QE

Nightly

Aurora / Dev Edition

Beta

Action items

Mobile

Performance

RelEng

Marketing/Communications

User Advocacy

Roundtable

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=

• Strings: https://bugzilla.mozilla.org/show_bug.cgi?id=1274712 marked as blocker for 49 now
• UI: https://bugzilla.mozilla.org/show_bug.cgi?id=1258041

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)

Actions