QA/SoftVision/Meetings/Desktop:2014-02-12

From MozillaWiki
< QA‎ | SoftVision‎ | Meetings
Jump to: navigation, search

Desktop QA Standup - February 12th, 2014

Dial-in Information

Attendees: Manuela, Anthony, mwobensmith, tracy, Henrik, Ioana, Petruta, Mihaela, Bogdan, Alexandra, Paul, Andrei, KaiRo, Catalin, Juan, Marc, Liz


Heads-Up

  • Upcoming PTOs:
    • Alexandra Lucinet - Feb 17th and 18th
    • Cornel Ionce - Feb 17th
    • juanb 2/13-2/18 PTO
  • Monday is Presidents Day in USA

Upcoming Schedule

  • Firefox 28.0 beta 3 to be released February 14th
  • Firefox 27.0.1 to be released February 14th
    • There are a few bugs under consideration in addition to the primary crasher driving this release. I'll have the test plan updated and ready to go with information about what fixes fianly make it into this non-urgent point release.

Channel Status

Beta (Fx 28)

Aurora (Fx 29)

Nightly (Fx 30)

  • [henrik] I see lots of plugin container crashes for Flash when opening vidyo in Nightly. Sadly without any crash report (only the Apple one). Anyone knows about it?
  • [juanb] Geo location problems on Windows?: https://etherpad.mozilla.org/Fx-Geolocation


ESR (Fx 24.4)

Security

  • Testing for X-Content-Security-Policy header, deprecation
  • Assessing Safe Browsing work

Automation

  • Mozmill 2.0.5 has been released this Monday which fixes restart tests on OS X. Sadly we are facing a new regression on Windows 8.1 (bug 970595) with the same symptomes mostly caused by changes of I/O completion ports
  • We cant make the goal to have Metro tests runningn on mozmill-ci production by today. But we have them running on Cosmins local machine under CI
  • We might have to drop the automation testday next week due to the work load regarding Metro and Firefox accounts

Stability

  • In overall volume 27 release looks good, maybe even a bit better than expected, but bug 934509 is probably quite nasty for those people who are seeing it, so it looks like we'll do a 27.0.1 for this one.
    • We have an ongoing discussion on the stability list about that bug, we caught this in QA in November, but dropped it on the floor on the way to release, which should not happen!
  • 28 beta 1 looked bad in overall volume, beta 2 has some fixes, including for the largest crash

(bug 965914), we hope that will look better.

    • some notable regressions show up in 27/28 comparison stats on beta:
      • bug 970483 (patch is on inbound now)
      • bug 952321 (patch has review, needs to land)
      • bug 963316 (could be a dupe of 952321, will need to see when that landed)

Previous Action Items

  • (in progress) - [juanb] Talk to web team (Raymond) to see if we can get news subscriptions for ** Raymond is researching this for now.
    • 2/13 Update from Raymond: "Stephen and I met with Craig on Monday to talk about feature work for QMO. Craig plans to work on this feature depending on the time he has available in the coming weeks. I’ll send out an update when we have something on dev for you to review."
  • [kairo] Waiting for data for new releases/versions of this week, will also do comparative analysis between 26/27 on release and 27/28 on beta later this week or early next week.

Discussion Items

  • Firefox 27.0.1 - two of the bugs supposed to get fixed here are still without fix. Are we going to wait for those fixes or are we surely getting the build tomorrow?
  • Feb 18, adopting new dev cycle. In what form?
    • Add any bugs that the Firefox team should work on as blocking bug 950073 and add [triage] to whiteboard
  • ashughes: Beta->RC->Beta automation support
  • ashughes: QAWANTED bug cleanup
    • Core, Toolkit, Firefox: http://mzl.la/1cwuVHW
    • can do this on the BMO back end without sending bugmail (or with)
  • mwobensmith: When is a bug marked verified when not verified on all branches?
    • A bug is marked Verified Fixed when verified on the target milestone version (regardless if also verified on other branches or not). OK, thanks.
  • Core/Platform will continue their current processes.
  • Australis and Sync also are NOT moving to this new dev cycle.

Notes and Actions

  • [ON TRACK] ashughes: drive regression testing for Geolocation, follow up with automation coverage once we know what the issue is
  • ashughes: publish a proposal for QAWANTED cleanup to the community
  • New dev cycle will start on Feb 18...(lots of details )
    • Where will they track sprint work? Meta bug?
    • "It will be tricky" -mschifer also "Expect chaos"