Firefox/Channels/Meetings/2016-04-26

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

lizzard, elan, kmoir, philipp, marco, kbrosnan, RyanVM, jorge, lmandel, sylvestre, calixte, guigs, marcia

  • Please welcome:
    • Marcia Knous as nightly release management
    • Marco Castelluccio will help to develop stability tools with Calixte


Previous Actions

Schedule Update

Congrats to releng, build promotion now on release....!

  • We have 11 tracked bugs, mostly crashes
    • one planned system addon update to Hello (without needing a release)
    • We may have a 46 dot release next week but it isn't certain.

WAY TO GO LIZ ON THE LATEST RELEASE HAT!!

  • 47 beta 1 built but needs a second build for the partials
    • release notes are reviewed and ready, will go live once 47.0b1 is signed off and pushed to beta channel

These issues delay aurora release. So we are slightly behind schedule for 48 aurora.


Add-ons

  • Bug 1267318 - Old add-on signatures being invalidated. We will probably might have to do a dot release for Firefox 46 and ESR. And likely for mobile.
    • Can we just resign the addons insteads?
    • dveditz and andy said this yesterday that wouldn't need a chemspill and wasn't a release blocker (it also affects users on 45.0.2 and older)
    • Can we push the change to the restriction to 47? (lmandel vidyo is borked. no mic or video right now) - how many addons are we talking about (we can also take this offline to a thread on r-d) (Andym is looking.)
    • What happens with the addons if they are invalidated? Can they still update to a newer version?


Stability

  • FYI. Project Uptime will be investigating crashes in nightly from dbaron's page, http://dbaron.org/mozilla/crashes-by-build
  • Uptime should address items like
    • ensure we have a good crash rate (with bsmedberg)
    • better identification of crashes that need to be fixed (weight crashes appropriately)
    • make crashes more actionable
    • get on top of newly identified crashes
    • develop tools to assist with all the above
    • (maybe) some crash fixing as well

Aurora

Overall rate (still for 47.0a2): 1.56 - browser: 0.9, content: 0.66 - yellow (target: 1.5)

  • volume of crashiness on aurora before the merge to 46 beta was 1.67

Beta

Overall rate (still for 46.0b): 1.15 - yellow (target: 1.0)

  • volume of crashiness on beta before the merge to 45.0 was 1.19

Release

Overall rate (still for 45): 0.97 - yellow (target: 0.95)

concerns from very early 46.0 data:

Mobile

Performance (Thu)

Aurora / Dev Edition

Beta

Release

QE

Nightly

Aurora / Dev Edition

Beta

Mobile

Performance

RelEng

Marketing/Communications

User Advocacy

Roundtable

  • prototype stability dashboard from bsmedberg...kairo signed off is there someone who understands it at the same level (erin) Can we judge/analyze e10s vs. non-e10s crash data from this?



Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

Sign Off (Thurs prior to GA Release)

Action items

Actions