Firefox/Channels/Meetings/2018-11-27

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.

Attendees

marcia, Liz, Pascal, Sebastian, philipp, tania, dveditz, wlach, RyanVM, Ritu

Schedule Update

Current releases dashboard: https://mozilla.github.io/delivery-dashboard

• 64.0b13 going out today

• 64.0b14 (last desktop build before RC) gtb tomorrow
  • webrender will be turned off

• remaining 64 blockers:
  • wnp: looks like it's being sorted this week, l10n through an agency - see https://bugzilla.mozilla.org/show_bug.cgi?id=1510065
  • frozen fennec: 65 has a tentative fix, but caused a crash; droeh's actively working on it
    • not completely sure this should block; initially marked 1496684 as blocking because it seemed new in 64, but

bug 1494748 is older

• plan for next week
  • RCs as needed for critical regressions/blockers
  • No channel meeting, ping us on slack #release-coordination or IRC #release-drivers

• m-b to m-r merge
  • Discussion on whether to do it this Friday or Monday of all-hands
    • Does this also affect m-c to m-b? There is a big refactoring scheduled to land Friday?
  • clang-format change planned for m-c for this Friday Paris daytime. If all goes well, merge on Friday am PST should not be a problem
  • Callek mentioned that Releng prefers to do the Merge on Mon, Dec 3rd.

Off-train releases

Current Shield studies: https://strategy-and-insights.mozilla.com/shield-studies/index.html

Stability

• Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1510293 for the missing Windows symbols

Nightly

firefox nightly summary score: 6.29, Thursday 6.94

• https://bugzilla.mozilla.org/show_bug.cgi?id=1509643 is quite visible in crash stats, but fixed by a WR pull request
• Mission Control Linux spike is due to https://bugzilla.mozilla.org/show_bug.cgi?id=1508096
• [wlach] note that buildhub still having problems (e.g. builds less than 24 hours old not showing up as I write this: https://mozilla-services.github.io/buildhub/?versions[0]=65.0a1), so nightly rates may still be slightly off. things improved from last week though.

Beta

firefox beta summary score: 2.15, Thursday 2.21

• Mission Control detected an increase in Mac content crashes, https://missioncontrol.telemetry.mozilla.org/#/beta/mac/content_crashes. Doesn't

seem to be a corresponding spike shown in Socorro

• • [wlach] not a lot of data on mac, looking at the data on an hourly level, not a big difference from previous betas: https://screenshots.firefox.com/a3HkvT4snAJzY4ES/data-missioncontrol.dev.mozaws.net (so probably a false alarm)

Release

firefox release summary score: 2.37, Thursday 2.43

• crash during auto-update with firefox monitor: https://bugzilla.mozilla.org/show_bug.cgi?id=1509352 - 35% of browser crashes in 63.0.1
• trend micro releasing a fix for the startup crashes in https://bugzilla.mozilla.org/show_bug.cgi?id=1490637 today - 1.3% of browser crashes

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: 25.45, Thursday 25.73

• https://bugzilla.mozilla.org/show_bug.cgi?id=1508740 is #4 overall, still waiting on a ni

• Beta

fennec beta summary score: 28.27, Thursday 29.09

• #4 overall https://bugzilla.mozilla.org/show_bug.cgi?id=1464902 seems stalled, no clues and affects Firefox as well

• Nightly

fennec nightly summary score: 45.72, Thursday 48.24

• Top browser crash https://bugzilla.mozilla.org/show_bug.cgi?id=1507513 is resolved fixed
• https://bugzilla.mozilla.org/show_bug.cgi?id=1499618 is now the overall #2 top crash
• #7 top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1505061 discussed during triage, will try to reproduce on one of the sites noted in the bug

Roundtable

• [overholt] number of content processes
  • https://wiki.mozilla.org/Electrolysis/Release_Criteria
  • This is for a small segment of release users
  • https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria#Stability
  • A study on a small segment of release64 users makes sense.