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
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.


lizzard, brad, ddurst, jlund, josh gaunt, lmandel, marcia, philipp, tom ritter, lmandel, shell, rail, RyanVM

Previous Actions

Schedule Update

  • beta to release merge was yesterday
  • 50.0RC should start the build today
    • Delayed to wait for patches from Bug 1313363 - notifications on android are truncated and bug 1313391
    • Will need an RC2 once we have a fix for blocking bug 1311462 - Symbol dumping failing for XUL on Firefox Beta 8 builds
  • 47.0.2 build 2 may ship today (websense + sse detection)
  • 45.5.0esr build started.


   1312779 in RC1 (MPC=True)
   do we need extra testing against Beta for SDK fixes?  or just making sure rides smoothly / monitor for bugs beyond testing already done?  
   where is suggested to monitor for issues?  
   watching firefox::extensions, toolkit::webextensions, toolkit::add-on SDK
   SUMO - shell follow up with Kris
   channels for Add-ons Zeber and metrics folks determined most likely metrics showing SDK changes - validating on nightly (big hunk of data already there) 
   adapt and run against beta end of week (need a few days for data) 
   before is Beta 9&10 (oct 21-26) / after is RC (because has MPC=true patch)


   blessed dashboard: AKA--> (sorry) via (
   more? [ddurst]
   comment in bug or start a thread
   Eli Perelman may be able to help with UX once the content is what relman needs
   Thanks for your work on this!
   [Action Item] Provide feedback if you think things are missing. UI feedback also welcome.


overall rate: 5.64 (browser 1.51, content 4.13) [marcia]

  • Top crash continues to be mozilla::plugins::AssertPluginThread, which is a won't fix

    • We should follow up on this offline and decide if it is worthwhile to reprocess the crashes. Marco mentioned it is an expensive process.
      • I've talked with Peter, and it looks like we can reprocess them (only ~10% weren't processed, so it shouldn't be too expensive).


overall rate: 0.98 (browser 0.80, content 0.18)



overall rate: 0.99 (browser 0.80, content 0.19)





Performance (Thu)

Aurora / Dev Edition





Aurora / Dev Edition


Action items



  • (rail) Webserse desupport warning


User Advocacy


Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)