Firefox/Channels/Meetings/2017-04-11
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
Contents
Attendees
lizzard, erin, philipp, josh g, mahe, dveditz, ritu, aki, others.....
Previous Actions
Schedule Update
- 53 beta 10
- 53 RC gtb on Monday Apr 10 (nearly ready, build 3 still in progress but build 1 has QE signoff)
- Likely ready to release 53 RC1 today.
- We already need an RC2 though. (Several sec bugs, crash related backout windows profile issue, etc.)
- Bug 1349076 - Do A/B testing of TLS 1.3 on Beta and Release (system addon a/b test to 1% release 52 users next week)
- ESR builds
- Gtb 52.1.0 yesterday - RelEng will investigate some pending task graphs
- Could the b10 top crasher also affect esr52? Bug # ??? crash: 1349847 (and others) cause: 1342433
- Gtb 45.9.0 when we have a patch for bug 1333858
Add-ons
Stability
Aurora
awsy rate: 8.21 (browser 1.53, content 6.67) telemetry (m+c-s) from saturday: 2.70 (3.26 the week before, 2.01 this time last cycle)
[philipp]
- BaseThreadInitThunk startup crashes rising since patch in https://bugzilla.mozilla.org/show_bug.cgi?id=1322554 landed - now nearly a quarter of all browser crashes on aurora
- patch is also approved for uplift to beta, but it may be too risky under these circumstances & we should wait and see how things progress in 54.0b
Beta
awsy rate: 0.78 (browser 0.60, content 0.18) telemetry (m+c-s) from saturday: 4.01 (4.31 the week before, 4.84 this time last cycle)
[philipp] early stability data for 53.0b10:
- top issue are crashes regressing from the uplift of bug 1342433:
- Crashes in mozilla::a11y::Accessible::HasGenericType: https://bugzilla.mozilla.org/show_bug.cgi?id=1349847 - 13.1% of browser crashes This is a release blocker level crash volume and I'm suggesting backout. - liz
- potentially mozilla::RefreshTimerVsyncDispatcher::NotifyVsync too: https://bugzilla.mozilla.org/show_bug.cgi?id=1350888 - 0.74% of browser crashes
- see also https://bugzilla.mozilla.org/show_bug.cgi?id=1321384
- crashes correlated to avast - 1.5% of browser crashes, 5.9% of content crashes
- (assigned, potential diagnostic patch not approved for 53) https://bugzilla.mozilla.org/show_bug.cgi?id=1346012
- (unassigned) https://bugzilla.mozilla.org/show_bug.cgi?id=1347523
- should we try to make sure that the patch for diagnostics gets into 54 at least and try some outreach to the vendor as well?
- crashes with lastpass (discussed in the "Release" section) - 3.4% of browser crashes, 2.9% of content crashes
- (assigned, fix going into rc) printing crashes regressing from bug 1311512: https://bugzilla.mozilla.org/show_bug.cgi?id=1347646 - 2% of browser crashes, 1.9% of content crashes
Release
awsy rate: 0.80 (browser 0.60, content 0.20) telemetry (m+c-s) from saturday: 2.79 (2.87 the week before)
[marcia]
- Significant crash spike in https://bugzilla.mozilla.org/show_bug.cgi?id=1354294 correlated to update of last pass addon. Currently #2 overall browser crash.
- 8.4% of browser crashes on release in the past couple of days and affects all branches
Nightly
awsy rate: 13.38 (browser 1.97, content 11.41) telemetry (m+c-s) from saturday: 5.20 (5.06 the week before, 11.42 this time last cycle)
[marcia]
- Top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1353420 involves the Gecko profiler
- https://bugzilla.mozilla.org/show_bug.cgi?id=1352827 is the Parser is still hanging around
- New crash https://bugzilla.mozilla.org/show_bug.cgi?id=1354637 has a review+ and just needs to be checked in
- New crash filed in mozilla::WidgetEvent::PreventDefault - https://bugzilla.mozilla.org/show_bug.cgi?id=1355497
Mobile
awsy rate: 1.15
[marcia] Fennec Nightly
- https://bugzilla.mozilla.org/show_bug.cgi?id=1351169 is still the top crash on trunk, has another ni but is moving slowly. 300 crashes/121 installs is fairly high for Fennec trunk
- A few signatures that may need bugs.
Fennec Release
- dalvik-main space 1 (deleted)@0xbbffffe signature is still pretty high - https://bugzilla.mozilla.org/show_bug.cgi?id=1286307. still a ni to investigate the fact that the crash rate dropped some, but not in beta
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
- 53 rc build3 is in good shape -- build1 and 2 had hg.m.o l10n issues, hopefully fixed for good
- looking into esr pending windows l10n tasks
- fennec 53 automation may be ready for gtb soon, need to double check
Marketing/Communications
User Advocacy
Roundtable
- Need to revert a string for 53, is this possible? https://bugzilla.mozilla.org/show_bug.cgi?id=1355534
The problem this is solving is that: the in-content insecure password warning we landed in 52, has some users thinking their computer has a virus
- l10n Dawn pivot is blocked on a public message; deadline is Friday but perhaps mitigation is to create their own messaging (?) In-product snippet plan.
- sumo update? (because inproduct links like https://support.mozilla.org/1/firefox/54.0a2/WINNT/de/npapi still don't work for me).
I'm going to add this to the meta: Yes, we are not at 100% yet Yes, :) The last remaining redirects for the 631 links should be pushed to production shortly.
- Stay calm and keep redirecting ;)
The process for new content is: https://bugzilla.mozilla.org/show_bug.cgi?id=1324426#c40