Firefox/Channels/Meetings/2019-01-24
From MozillaWiki
Channel Meeting Details
- Tuesdays 10am and Thursdays at 8am 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
marcia, RyanVM, Callek, ritu, sylvestre, pascal, philipp, lizzard,tania, mtabara, Sebastian
Schedule Update
Current releases dashboard: https://mozilla.github.io/delivery-dashboard
- Desktop 65.0 RC1 live on Beta @ 100%, Fennec 65.0 RC1 live on Release @ 5%
- 65.0 RC2 gtb today (Desktop & Fennec)
- DevEdition 66.0b2 gtb today
- 60.5esr build2 gtb today
- 60.5esr build1 had broken search on non-en-US locales
- what was the regressing bug? search codes update in 1510296
- 60.5esr build1 had broken search on non-en-US locales
- Merge day on Monday, 28-Jan
Off-train releases
Current Shield studies: https://strategy-and-insights.mozilla.com/shield-studies/index.html
Stability
- MC Windows issue - https://bugzilla.mozilla.org/show_bug.cgi?id=1521851. The issue seems to have gone away
- content crashes properly reported in nightly again: https://bugzilla.mozilla.org/show_bug.cgi?id=1521801
Nightly
firefox nightly summary score: 3.60 , Tuesday 3.79
- Core | DOM spike which started in 1-22 builds - https://bugzilla.mozilla.org/show_bug.cgi?id=1522109
- Looks as if this will be fixed by a backout as well
- New small volume Font regression https://bugzilla.mozilla.org/show_bug.cgi?id=1522416
- Core | Networking regression https://bugzilla.mozilla.org/show_bug.cgi?id=1522076 looks to be fixed by a backout
- Most Recent Nightly Crash Triage: https://wiki.mozilla.org/NightlyCrashTriage/2019Q1
Beta
firefox beta summary score: 1.32, Tuesday 1.36
- 65.0rc1 looking good - no particular concerns
- 66.0b1
- tab crashes in mozilla::gfx::DrawTargetD2D1::CreateBrushForPattern: https://bugzilla.mozilla.org/show_bug.cgi?id=1521368 - 17% of content crashes
Release
firefox release summary score: 1.69, Tuesday 1.72
- tab crashes with ms library for vp9 playback on win10 1809 N editions rising since last week: https://bugzilla.mozilla.org/show_bug.cgi?id=1521370
- Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1522524 to account for a possible telemetry crash in 64.0.2
Mobile
- Crash rate is calculated based on usage hours (the time Firefox is actively used).
- Usage hours will be significantly lower on Fennec than on desktop Firefox, so we can't compare mobile rates to desktop rates.
- Release
fennec release summary score: 24.85, Tuesday 25.11
- No new crashes in the top 20
- https://bugzilla.mozilla.org/show_bug.cgi?id=1502817 seems to be rising a bit
- Beta
fennec beta summary score: 31.99, Tuesday 31.95
- Snapdragon issues in the latest builds
- https://bugzilla.mozilla.org/show_bug.cgi?id=1521398 appears to have surfaced again in the RC.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1492206 has surfaced as the top crash in B13 so far, but I don't see it the RC
- RyanVM to email release-drivers today with an update that this is putting the Fennec release at risk
- Snapdragon issues in the latest builds
- Nightly
fennec nightly summary score: 64.35, Tuesday 67.32
- JS crash https://bugzilla.mozilla.org/show_bug.cgi?id=1521158 has risen to #2. Seems not much we can do about it at the moment
- Otherwise nothing specific to call out for Nightly
QA
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile Stability
SUMO Report / User Advocacy
Roundtable
- [wlach] working on a 2019 roadmap with some thoughts about and ideas for mission control and release monitoring based on what I've heard, will do a request for feedback soon
- [jcristau] \o/