Firefox/Channels/Meetings/2013-05-09

From MozillaWiki
Jump to: navigation, search

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)
  • irc.mozilla.org #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
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.

Previous Actions

Schedule Update

  • FF21.0b7 for desktop shipped
  • FF21.0b8 for mobile shipped (pending update sign-off)
    • Bug 868826
  • FF 21.0 RC builds for Mobile and Desktop with QA

Add-ons

  • Nothing new for add-ons.

Stability

Aurora

  • Again, no concerns left on Aurora 22.

Beta

  • https://bugzilla.mozilla.org/show_bug.cgi?id=851934 (outlook.com) continues to be a concern across channels. jandem is working with the user now to find a fix.
  • https://bugzilla.mozilla.org/show_bug.cgi?id=836263 (Crossrider) seems to drop off the topcrash lists very fast now - #6 in 7-day topcrashes, #8 in 3-day, #159 (!) yesterday on 20
  • Preliminary data on 21.0b7 suggests that all data looks pretty much as usual, the signatures that rose up in b6 are off to top ranks, js::GCMarker::processMarkStackTop is back to its usual #2 position.

Release

  • https://bugzilla.mozilla.org/show_bug.cgi?id=838568 (Brazil banks) is rising into the top 10 now on 20, but we also now have some dialog in the bug with the company creating those libraries (GAS). They claim that the problem would be in proxy code changes in Firefox 18, and a new version of their software is in the slow bank-approval process that should fix things.

Mobile

  • No specific concerns, will need to take a look over the weekend how stagefright crashes develop in 21.0b8.
  • Bug 863980 - java.lang.IllegalStateException: Couldnt read <rc> from CursorWindow. Make sure the Cursor is initialized correctly before accessing data from it. at android.database.CursorWindow.nativeGetString at org.mozilla.gecko.AllPagesTab.storeFaviconsInMemCache
  • It looks like Vivante graphics crash bug 863313 and bug 863307 might be the same

QA

Desktop

Mobile

RelEng

  • still having difficulties getting QA access to 21.0 build2 bits for automation. If we can't find a solution can we just stop blocking ?
  • fyi - new update server, Balrog, is a Q2 goal for Releng. We're aiming to switch to it by the end of quarter, just for the *nightly* channel. Does after the June 24 merge sound fine ?
    • Yes

Marketing/Communications

Nothing this week - had to drop off. Let us know if the timing for 21 changes.

Support

  • Collecting feedback on release, snippet survey?

Thunderbird (Tue)


Metrics (Thu)


Roundtable

  • Brainstorm - minimum viable contributor descriptions in support of releases, for instance:

"Description: Support users on the Aurora channel. Focused support helper for people who are running the Aurora channel to help them turn support requests into useful bug reports. Details: talk to djst or mgrimes."

  • Other ideas:
    • Run the pre-release channels and update regularly- Nightly (devs, web devs, bleeding edge, daily updates), Aurora (cutting edge, still rough around the corners, daily updates), and Beta (weekly RCs, much like being on Release)
      • From stability POV: Emphasis would be good on getting more people to test on Aurora (unless they are on Nightly already)
      • Advanced Features - 3d, web developer tools, 3d shooters, your favorite add-on
    • Read the release notes, test features, and provide feedback through Input/SUMO/Bugzilla
    • Make sure crash reporting, Telemetry, and FHR are enabled for passive feedback
    • File bugs (requires BZ account) that you believe to be new issues and critical, and nominate with the correct Firefox version tracking flag, providing as much information and steps to reproduce as possible
    • help participate in testdays
    • testing add-ons in pre-release channels (add-on compatibility reporter), binary add-ons right after their release (our most problematic, avg, skype, etc.)
    • sumo input trend finders and investigators (version regression, web regression, 3rd party regression)
    • verifying website issues
    • Tech Evangilism outreach (like mobile)
    • Watching components, reproducing, tracking noms - plugins, regressions,
    • finding early testing in interesting environments (enterprise, weird networks)
    • crash+qawanted

we need to get the following page updated http://www.mozilla.org/en-US/firefox/releases/ to include the latest release notes bug 870305 filled out for tracking it

Actions

Triage

Aurora Queries

Beta Queries

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Channels/Meetings/2013-05-09&oldid=654533"