From MozillaWiki
Jump to: navigation, search

Channel Meeting Details

Video/Teleconference Details - NEW

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.


RyanVM, jcristau, telin, pascalc, ritu, tania, TomGrab, dveditz, overholt, tomprince

Schedule Update

Current releases dashboard:

  • 65.0b5 shipped to all channels today
    • Fennec @ 99% rollout still (waiting to see what bug 1513870 does)
  • 65.0b6 gtb Thursday (Desktop & DevEdition only)
  • Holiday Beta schedule:
    • 65.0b7 gtb Thursday, 27-Dec for all products
    • 65.0b8 gtb Thursday, 3-Jan for all products
    • Back to normal schedule on Monday, 7-Jan

Off-train releases

Current Shield studies:



firefox nightly summary score: 16.98, Thursday 5.22

the issue was backed out of nightly for failing tests


firefox beta summary score: 2.90, Thursday 9.02


firefox release summary score: 2.68, Thursday 5.79


  • 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: 29.22, Thursday 25.09

due to the tremendous crash volume we had in 63.0.1.

  • Beta

fennec beta summary score: 44.84, Thursday 221.17

triage today we discussed we are unsure what caused this issue and there are theories about a corrupt build

  • Nightly

fennec nightly summary score: 34.30, Thursday 31.58

    • Nothing of note to call out for nightly



Aurora / Dev Edition


Action items

Mobile Stability

SUMO Report / User Advocacy


  • win64-aarch64 nightlies
    • mark them as "experimental"? Pascal suggested doing a Nightly blog
    • note something on about this platform?
    • probably OK as long as expectations are managed (not linked from regular nightly download page, noted as experimental)
      • ASAN reporter builds have similar messaging around them
    • Overholt discussing with Chuck about what comms we might need on this
    • Pascal offered to coordinate Twitter activity
    • Currently no hardware and not enough people to test this in QA. We expect to receive hardware in January/February, but in order to test Nightiles we will have to move QA engineers from other tasks, so we would need to decide what else to drop to accommodate arm64 testing. Our automation tools don't work on ARM64 at the moment, so all testing has to be manual.

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)