Firefox/Channels/Meetings/2017-05-30

Channel Meeting Details

• Tuesdays and Thursdays at 10am Pacific Time
• irc.mozilla.org #planning for backchannel
• Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

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: ReleaseCoordination
• Vidyo Guest URL

Attendees

jcristau, dveditz, philipp, marco, marcia, ritu, milan, mahe

Previous Actions

Schedule Update

• 54.0b11 (desktop) shipped on Friday
• 54.0b12 beta+devedition shipped today
• next week is RC week

Add-ons

Stability

Nightly

awsy rate: 2.14 (browser: 1.35, content: 0.79) telemetry (m+c-s) from saturday: 5.44 (week before: 5.24, this time last cycle: 7.32)

[marcia]

• Nightly crash rate in the high range, but slightly lower than what was reported last Thursday
• https://bugzilla.mozilla.org/show_bug.cgi?id=1367742 spiked when RCWN was turned on - it was turned off on Friday.
• https://bugzilla.mozilla.org/show_bug.cgi?id=1363630 shows as spiking on Nightly, but all the comments say "test" - maybe related to some automation we are running?
  • i get the same signature when artificially crashing with the help of https://addons.mozilla.org/de/firefox/addon/crash-me-now-simple/
• https://bugzilla.mozilla.org/show_bug.cgi?id=1367806 - new bug that emerged, patch is attached.
• https://bugzilla.mozilla.org/show_bug.cgi?id=1356853 spiked, phillip thinks a single user caused the spike
• Stylo landing likely cause of https://bugzilla.mozilla.org/show_bug.cgi?id=1368690
• New Uptime bugs: https://wiki.mozilla.org/Platform/Uptime/NightlyCrashTriage/2017Q2#2017-05-29_-_njn

https://bugzilla.mozilla.org/show_bug.cgi?id=1365123 telemetry m+c rate much higher in 55 than previous cycles? For Beta, Release we look at m+c-s.

Beta

awsy rate: 0.73 (browser: 0.51, content: 0.22) telemetry (m+c-s) from saturday: 4.22 (week before: 4.12, this time last cycle: 4.31)

[philipp] 54.0b11:

• Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError... | mozilla::devtools::PHeapSnapshotTempFileHelperChild::Write newly appearing in b11: https://bugzilla.mozilla.org/show_bug.cgi?id=1368343 - 0.5% of content crashes
• Crashes correlated to Avast now showing up as [@ TriggerPromiseReactions] after diagnostic patch landed on b11: https://bugzilla.mozilla.org/show_bug.cgi?id=1347984 - 0.6% of browser crashes, 3.4% of content crashes

• Crashes from the new beta-based DevEdition are currently showing up as version 54.0 (not 54.0b) in socorro data: https://crash-stats.mozilla.com/search/?release_channel=aurora&product=Firefox&version=54.0#facet-signature
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1368632

Release

awsy rate: 0.71 (browser 0.52, content: 0.19) telemetry (m+c-s) from saturday: 9.43 (week before: 10.35, this time last cycle: 2.87)

• [philipp] very high telemetry browser-process crash rate since 53.0.3 (4x what we've had on 53.0.2 and before)
  • windows 7 installations with a shutdownhang like in https://bugzilla.mozilla.org/show_bug.cgi?id=1267692 - no corresponding increase noticeable in socorro at all
  • working theory is some bot-/automation-farm gone haywire

• Explosiveness report shows some hang and flash issues: https://crash-analysis.mozilla.com/release-mgmt/2017-05-29/2017-05-29.firefox.53.explosiveness.html

Mobile

awsy rate: 0.67

[marcia]

• Release mobile crash rate looks good.
• Nightly rate looks good
  • njn filed https://bugzilla.mozilla.org/show_bug.cgi?id=1368377, new crash in nightly

Performance (Thu)

Aurora / Dev Edition

Beta

Release

QE

Nightly

Aurora / Dev Edition

Beta

Action items

Mobile

RelEng

Marketing/Communications

User Advocacy

• [philipp] OCSP issue various MS web properties (Hotmail, Bing, MSN...) exclusively locking out firefox users: https://bugzilla.mozilla.org/show_bug.cgi?id=1368433
  • https://portal.office.com/servicestatus
  • Ekr has reached out to Microsoft today

Roundtable

• Process changes for Multiple Signoff in Balrog (bhearsum)
  • Publishing updates will require humans to formally signoff in Balrog, and happen automatically at a set time.
    • Currently planning to require RelEng + RelMan signoff to ship to beta, release, or esr. May need to allow QA to signoff on beta?
    • This can (should?) replace the "please push" e-mails that currently go to release-drivers.
  • Other parts of publishing (Bouncer, marking in Ship It, version bumps) are the same as before.

[marcia]

• In Nightly, should we be allowing https://bugzilla.mozilla.org/show_bug.cgi?id=1367390 to happen late in the cycle. Worried that turning it on for a few days will possibly carry into next week
  • Dragana mentioned it's waiting for review from Patrick. Let's ask them to land it latest by today. Otherwise they need to hold off to post-merge.

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)

Actions