From MozillaWiki
Jump to: navigation, search

For 9/12 (don't delete): 886543 – Add capability for unsupported update.xml 843497 – Update check says "up to date" for out of date versions on unsupported OS versions Channel Meeting Details

  • Tuesdays at 10am PDT, and Thursday at 2:00pm PDT
  • Mountain View Offices: Warp Core Conference Room
  • San Francisco Office: SFO-7I Independent (Tues), Noise Pop (Thurs)
  • #planning for backchannel

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: Release Coordination
  • 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.

Previous Actions

  • carry over : nothing to report on beta -> release -> beta test yet (bug 908134), staging systems are busy
  • Relman : Week of Summit : Oct 4 - 6 planning on schedule

Schedule Update

    • FF24.0b10 have gone to build as of yesterday


  • No updates.



  • investigation for Bug 800347 - crash in mozilla::ipc::RPCChannel::OnMaybeDequeueOne


  • Bug 912110 - crash in nsXPCWrappedJS::Release() with DatamngrHlpFF24.dll (Bandoo)
    • Bandoo is engaged
  • see below


  • No concerns.




Verification Needed

Aurora (ashughes)

  • no blockers to Beta migration on QAs radar at this time

Beta (tracy)

option #1: - No New Info as of this morning

  • More info/updates in Bug 911502
    • We get any new information that more than one user is able to reproduce
      • In which case we will still stick the recent backout and no need for an additional beta

option #2: - has builds up , needs user testing (might know tomorrow)

option #3:

  • There has been some back-forth on whether the patch in fixes the issue at all ?
    • Discuss that in the channel meeting and get clarity on STR and everyone on the same page
      • If we are at consensus that we are better off landing the forward fix and taking a risk for a possible issue in Bug 911502 in case option #1 & #2 don't work, then another beta may be required (FX24.0b11)
  • If we with the above due to the limited data in hand, mitigation strategies ?


Firefox 24 Beta 10

  • Still able to reproduce (with a little more effort required this time around) bug on mozilla-beta and mozilla-aurora; mail sent to release-management and commented in bug
  • Ship as is with current frequency (1/8?)
  • Respin a beta with the upstream patch (this is what maire and jesup recommend)
    • Theory from Jesup: patch from Bug 899159 is the difference between mc and mb behavior
    • Also, "upstream patch" and has been reviewed by Google
  • Nightly updates have been broken for 4 days - 913842 - Resolved fixed Could use a respin




Firefox 24 Beta Survey results are in, 4.0 star average rating

Thunderbird (Tue)

Metrics (Thu)


  • [akeybl, read-only] cert post-mortem is being held tomorrow at 8AM PT in the ReleaseCoordation vidyo room
  • Release Sign-off meeting on Thursday's Channel meeting
  • [bsmedberg] Marking all versions of Java unsafe in Firefox 24 - filed bug 914690


  • Action on :bajaj to talk to jesup and others for WebRTC