Firefox/Channels/Meetings/2019-05-07

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

Attendees

RyanVM, ritu, dveditz, marcia, lizzard, telin, Aryx, jcristau, philipp, tmaity, tomgrab, SolidSnake

Schedule Update

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

All the arnagadd-on you could ever want:

• 66.0.4 released Sunday
  • 25% for 12 hours, 100% for 30 hours, 0% now
• 66.0.5 in flight, ETA: Likely today, May 7th

• ESR60.6.2 released Sunday
  • same as 66.0.4
• 60.6.3 in flight, ETA: Likely tomm, May 8th

• 67.0b17 released Monday
• 67.0b18 released just now

• https://bugzilla.mozilla.org/show_bug.cgi?id=1549718 can cause data loss when updating to 66.0.4 / 60.6.2, and is the reason we're back at 0% for now

• merge was tentatively moved from May 6 to May 8, TBC

• For both related and unrelated reasons, nightly updates were turned off for pretty much the whole weekend. That means 68 is not in the happy state it should be in its last week on nightly.

Off-train releases

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

Stability

• Some reports from over the weekend are being reprocessed - see https://bugzilla.mozilla.org/show_bug.cgi?id=1549318
  • calixte found another set that will need to be addressed due to another bad processor node. That should now be fixed as well
    • Can we get alerting for this so we don't have to "find" these types of issues
      • Lessons learned from the incident - Socorro needs to be fully functional

Nightly

firefox nightly summary score: 7.17, Thursday 6.50

• Top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1547911 was resolved fixed. Affected Desktop and Mobile
  • Crash volume was way too high (22,400K) and I am not sure that the developer understood the magnitude of the situation
  • New signature https://bugzilla.mozilla.org/show_bug.cgi?id=1549373 now showing up
• Fission related crash in Content Processes - https://bugzilla.mozilla.org/show_bug.cgi?id=1549580

Beta

firefox beta summary score: 2.83, Thursday 2.93

[67.0b17]

• Content crash in [@ mozilla::dom::ClientSource::SetController]: https://bugzilla.mozilla.org/show_bug.cgi?id=1535699 - 5.1% of tab crashes
  • last comment was that more diagnostics are needed
  • message from Asuth: " perry has a local repro with rr trace and is actively pursuing. (And I'm also making sure I understand so I can do a fast sign-off and maybe help out with tests.)"
  • bugs with the same signature & str are https://bugzilla.mozilla.org/show_bug.cgi?id=1547524 & https://bugzilla.mozilla.org/show_bug.cgi?id=1549580
• https://bugzilla.mozilla.org/show_bug.cgi?id=1535301 - 1.5% of browser crashes

Release

firefox release summary score: 1.82, Thursday 1.83

[66.0.4]

• https://bugzilla.mozilla.org/show_bug.cgi?id=1525078 continues to be visible in both release and beta, but comments mention there is not much we can do about it

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: 16.29, Thursday 16.50

• • Nothing new in the top 20.

• Beta

fennec beta summary score: 50.27, Thursday 55.85

• • Mission Control rate is high, but latest betas don't seem to have explosive spikes
    • https://bugzilla.mozilla.org/show_bug.cgi?id=1521158 is still around in b16 so that may be a contributing factor
    • Still early for b17 https://crash-stats.mozilla.com/topcrashers/?product=FennecAndroid&version=67.0b17&process_type=any

• Nightly

fennec nightly summary score: 126.02, Thursday 95.87

• • https://bugzilla.mozilla.org/show_bug.cgi?id=1547911 affected Fennec as well, likely causing the increased crash rate
    • This crash was causing some people to crash when they pressed the back button

QA

• Dot Release: QA results are tracked here: https://docs.google.com/document/d/17Td7VOlzlWoH-z7xTCrS8Yx4y2oS1YJn5uMqD7dt9bw/edit#heading=h.tyhchnutpl57
  • 66.0.5 RC - Finished
  • 67.0b18 Beta - Finished
  • 60.6.3esr - Finished
  • 68.0a1 - Finished
• Argentina team has taken over functional tests and update tests for 66.0.5-build1

Nightly

• Nightly Regression testing is in progress

Aurora / Dev Edition

Beta

Action items

Mobile Stability

SUMO Report / User Advocacy

• seeing a handful of users reporting connectivity issues after addons got reenabled after amogaddon: https://mozilla.slack.com/archives/CJGBVE4G6/p1557177645107400

Roundtable

• restricted beta uplifts on Thursday? owner needed. sheriffs don't have access, Aryx traveling and not available before European evening
  • Ryan or Julien can help where needed
• Public holiday in France tomorrow (julien, pascal out).
  • [Thomas] who's covering the Cross Functional slides?
    • 67 - Ritu, 68 - Ryan
• [marcia] Is there a link for the post mortem or a place we can drop thoughts?
  • Relman will create their own document and drop thoughts for the Post Mortem
• [Thomas] Summative update and next steps for Armagaddon Certastrophe in the Cross Functional

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)