Firefox/Channels/Meetings/2017-07-18
Channel Meeting Details
- Tuesdays and Thursdays at 10am Pacific Time
- irc.mozilla.org #planning for backchannel
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
Contents
Attendees
jcristau, ritu, mihai, kevin, marcia, ben, philipp, lizzard, nicole, shell, dveditz
Previous Actions
Schedule Update
- 55.0b9 shipped friday (desktop)
- 55.0b10 shipped today (desktop+fennec)
- screenshots will go 100% on beta soon
- e10s-multi should be at 50% on beta 9/10
Add-ons
Stability
[marcia]
- We need Mac 10.13 symbols. marcia to work with ted to get them from her machine, and then upload them to the symbol store
- https://bugzilla.mozilla.org/show_bug.cgi?id=1340959#c5 suggests we will see a crash spike in this signature on Android
- Some suggestions were made on the stability list regarding tweaking email notifications of crashes to better call out large spikes
- if you need someone to rebuild nightly over the weekend ask on #sheriffs, #releng, then escalate to relman
Nightly
awsy rate: 9.55 (browser: 2.62, content: 6.94) telemetry (m+c-s) from saturday: 20.15 (last week: 7.21, this time last cycle: 5.24)
[marcia]
- One regression caused a large crash spike on Nightly - it was backed on Sunday night by Nicholas Nethercote. Over 5K in crashes.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1380267 spiked and the developer has been notified. This is currently the top browser crash in the last 7 days
- Stylo crash https://bugzilla.mozilla.org/show_bug.cgi?id=1381475 moved up in the upper regime of crashes, due to a release assert that was added in another bug
- Explosiveness report: https://crash-analysis.mozilla.com/release-mgmt/2017-07-17/2017-07-17.firefox.nightly.explosiveness.html
- https://bugzilla.mozilla.org/show_bug.cgi?id=1374792 is fixed, but there are remaining crashes that will likely need a new bug
- Some reports of users having issues using GMail in Nightly
Beta
awsy rate: 0.94 (browser: 0.70, content: 0.23) telemetry (m+c-s) from saturday: 4.79 (last week: 4.57, this time last cycle: 4.12)
[philipp] 55.0b9
- Crash during shutdown in mozilla::ipc::MessageChannel::Clear | ... | mozilla::dom::PContentParent::~PContentParent: https://bugzilla.mozilla.org/show_bug.cgi?id=1363601 - 4% of browser crashes
- increased in b9, blocked on a ni for two months
- Cluster of JS crashes regressing in 55: https://bugzilla.mozilla.org/show_bug.cgi?id=1373934 / https://bugzilla.mozilla.org/show_bug.cgi?id=1374702 - 2.6% of browser crashes
- Intel graphics driver crashes: https://bugzilla.mozilla.org/show_bug.cgi?id=1359416 - 1.8% of browser crashes
Any obvious results from turning on e10s multi in beta 9? Beta Performance telemetry (from first 2 days) didn't show any stand-outs. https://metrics.mozilla.com/protected/bmiroglio/multi/55/e10sMulti_experiment.html . Need a few more days for visibility in Beta stability chart to start showing up (7 day delay - first day July 14th) https://sql.telemetry.mozilla.org/queries/5483#11140
Release
awsy rate: 0.80 (browser: 0.57, content: 0.23) telemetry (m+c-s) from saturday: 2.85 (last week: 2.75)
[marcia]
- Explosiveness report is pretty quiet: https://crash-analysis.mozilla.com/release-mgmt/2017-07-17/2017-07-17.firefox.release.explosiveness.html
- #2 overall top browser crash related to (Comodo, Windows 10) should be fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1376831
Mobile
awsy rate - release 0.59, beta 1.16, nightly 1.87
[marcia]
- Mobile looks good across all three channels.
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
- (bhearsum) Enabling signoffs for all the things (Firefox release/esr, GMP, SystemAddons) **tomorrow**
- (liz) suggesting ryanvm, anthony hughes, kamil, tracy as QE signoff backup for US time zone coverage (in case of weekend/chemspill situations)
Marketing/Communications
User Advocacy
Roundtable
- (elan) Looking at e10s multi 54 data while we were for sure enabled in Aurora, and also the data we have so far for 55, we don't have any reason *not* to go to 1% of the population in 54. Blake is readying a patch and RyanVM is working closely with Grover to get the the fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1380725 tested.
We don't know when the changes to the system add-on will be made and tested, once we have an ETA, we will share.
- Black Hat & Def con are coming up right at the end of July (large security conferences, new issues may be reported )
