Firefox/Channels/Meetings/2017-05-23
From MozillaWiki
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
REMEMBER
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.
Contents
Attendees
jcristau, mtabara, marcia, ritu, erin, nicole, mahe, philipp, lizzard
Previous Actions
Schedule Update
- 53.0.3 and 52.1.2esr shipped Friday
- ntlm still apparently problematic
- 54.0b10 desktop released
- 54.0b10 fennec released at 10% (testing staged rollout in advance of 55.0b1)
Add-ons
Stability
[marcia]
- No Android nightlies for several days. Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1366729
Nightly
awsy rate: 2.46 (browser: 1.24, content: 1.22)
- Rate is down slightly from Thursday
- Small spike in https://bugzil.la/1366812. Patch has been backed out
- https://bugzilla.mozilla.org/show_bug.cgi?id=1361132 - Pinged Microsoft again today regarding this
- https://bugzilla.mozilla.org/show_bug.cgi?id=1360029 rose slightly
- New Uptime crashes filed: https://wiki.mozilla.org/Platform/Uptime/NightlyCrashTriage/2017Q2#2017-05-22_-_marcia
Beta
awsy rate: 0.76 (browser 0.54, content 0.22)
[philipp] 54.0b9:
- (assigned, fix in b10) Crash in mozilla::layers::MaybeTimeDuration::AssertSanity: https://bugzilla.mozilla.org/show_bug.cgi?id=1363107 - 6% of browser crashes
- (assigned) Crash in EnqueuePromiseReactionJob: https://bugzilla.mozilla.org/show_bug.cgi?id=1347984 - 0.7% of browser, 3.6% of content crashes
- partly correlated to avast & volume slightly declining on its own; diagnostic patch landed on nightly today
- Startup crash mozilla::Preferences::AddBoolVarCache showing up on b9 - waiting for how that's developing in b10 before filing a bug: https://crash-stats.mozilla.com/signature/?product=Firefox&release_channel=beta&signature=mozilla%3A%3APreferences%3A%3AAddBoolVarCache
Release
awsy rate: 0.69 (browser 0.50, content 0.19)
[marcia]
- Explosiveness report: https://crash-analysis.mozilla.com/release-mgmt/2017-05-22/2017-05-22.firefox.53.explosiveness.html
- filed https://bugzilla.mozilla.org/show_bug.cgi?id=1367128 for the OOM crash in media code on twitch.tv
- #5 top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1267997 rose slightly
Mobile
awsy rate: 0.68
- Release Explosiveness Report: https://crash-analysis.mozilla.com/release-mgmt/2017-05-22/2017-05-22.fennecandroid.release.explosiveness.html
- Longstanding Bug https://bugzilla.mozilla.org/show_bug.cgi?id=760394 is #2 overall on release
- Dalvik Bug is #3 https://bugzilla.mozilla.org/show_bug.cgi?id=1286307
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
Marketing/Communications
User Advocacy
Roundtable
- Proposed plan of record for e10s multi
- Roll out to no-add-ons in 54 release (62% of our population)
- 20% would stay single process
- 80% would be converted to multi
Striking plan to include WebExensions because of concerns about stability We are testing MPC = true in beta but there isn't a plan to go to release yet
- still hoping to land speed fixes for WebExtensions load and Out of Process in 55 https://public.etherpad-mozilla.org/p/webextensions-perf-status
- looks like fix to Crash in EnqueuePromiseReactionJob helped with Nightly on the crashes that were impacting WE stability - can wait to see if uplifted to Beta
- No specific e10s-multi staged rollout planned when 54 goes live other than release staged rollout (i.e. day1 - 25%, day 2 - disabled, day 3 - 100% if all goes well)
- If we need to rollback, we will use the e10s rollout system add-on and *not* need to do a dot release
