Firefox/Channels/Meetings/2016-09-13

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

  • blassey, callek, erin, lmandel, calixie, liizzard, philipp, marco, lmandel, ryanvm, ritu, milan, davidb, jet, dveditz, hwine

Previous Actions

Schedule Update

  • 49 RC3 desktop build Monday (yesterday) Released today.
  • 49 RC2 mobile build Monday.

Main driver is the slow script warning. https://bugzilla.mozilla.org/show_bug.cgi?id=1284511#c54

  • (Ryan) Bug 1299593 - Microsoft Dynamics CRM 2011 Lookup Error since Firefox Version 48.0.2 due to Array.prototype.values
 - Should we block 49 on this? https://bugzil.la/1299593

IT head's up: IRCCloud (not IRC) outage from 1000-1300 PT On Saturday. If you expect to need IRC for coordination on 49, please make other plans or escalate to #moc (hwine) - https://whistlepig.mozilla.org/en-US/detail/782/



Add-ons

Stability

Aurora

Beta

overall crash rate: 1.10; browser: 0.96, content: 0.14

  • [philipp] rc2 crash data generally looks good
  • how are we going to deal with websense users & the 49 update? (crashes from bug 1294650 are still present in 49.0 builds)
  • (liz) I was planning to leave users before 48, still not updating to 49.


Release

overall crash rate: 0.88; browser: 0.77, content: 0.11

Nightly

[marcia]

Mobile

[marcia

Performance (Thu)

Aurora / Dev Edition

Beta

Release

QE

Nightly

Aurora / Dev Edition

Beta

Action items

Mobile

Performance

RelEng

Marketing/Communications

User Advocacy

Roundtable

[elan]

  • Enabling e10s multi in Nightly as of 52
   probably got to Aurora and then stop there (?) 
   we need to create a plan of attack

Are we worried about stability?

   worried about memory use and functional breakage
   issues with service workers; we think they are edge casey 
   one of the other thing: user perception of stabiliy is a big deal
   this first initial landing will be 2 content processes - until we eventually 



Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)

Actions