Firefox/Channels/Meetings/2017-05-30

From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

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: ReleaseCoordination
  • 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

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]

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:

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)

Mobile

awsy rate: 0.67

[marcia]

Performance (Thu)

Aurora / Dev Edition

Beta

Release

QE

Nightly

Aurora / Dev Edition

Beta

Action items

Mobile

RelEng


Marketing/Communications


User Advocacy

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