Firefox/Channels/Meetings/2018-08-21

From MozillaWiki
Jump to: navigation, search

Channel Meeting Details

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

RyanVM, elan, telin, tomgrab, kbrosnan, aryx, tomprince, overholt, dveditz

Schedule Update

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

  • 62.0b19 shipping today to Desktop, DevEd, and Fennec.
  • Nightly 63 soft freeze starts Thursday

Off-train releases

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

Stability

Nightly

firefox nightly summary score: 4.07, last Thursday 4.04

Beta

firefox beta summary score: 2.41, last Thursday 2.46

Release

firefox release summary score: 2.22, last Thursday 2.26

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: 27.62, last Thursday 27.83

  • Beta

fennec beta summary score: 30.22, last Thursday 30.62

    • Fennec beta looks good overall. One API 21 crash spotted specific to b17, but not sure worth filing since it is very low volume
  • Nightly

fennec nightly summary score: 48.14, last Thursday 47.85

QA

Nightly

Aurora / Dev Edition

Beta

Action items

Mobile Stability

SUMO Report / User Advocacy

Roundtable

  • (telin) Do we know how sensitive the Mission Control crash rates are to new spikes given the time frame they're averaged over?
    • (Ryan) I believe we've successfully correlated new topcrashes to visible spikes in the rate previously
    • Unsure whether there would be a benefit to a shorter-timeframe rate which might be more sensitive to recent regressions
    • Has the data science team reviewed the current calculations?
      • (elan) There's a core product metrics team which hasn't been as active recently, might be something for them to review
    • We do have daily crash triage happening, so any new crash signatures should be getting caught still since that triage isn't rate-dependent

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)