QA/SoftVision/Meetings/Desktop:2014-03-19

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

Desktop QA Standup - March 19th, 2014

Dial-in Information

Attendees: Manuela, Cornel, Matt, Nils, tracy, Alexandra,Otilia, Ioana, Petruta, juanb, Mihaela, Andrei, Paul, Bogdan, Catalin, KaiRo, Liz, Kamil, Henrik

Heads-Up

  • Upcoming PTOs:
    • Mihaela Velimiroviciu - March 28th and 31st
    • Nils Ohlmeier - March 26th to 28th
  • Events

Upcoming Schedule

Channel Status

Beta (Fx 29)

  • Metro not yet disabled. Accordin to :jimm, it will only happen "next week or so".
  • Last moment changes done for the UI Tour. The changes weren't mentioned anywhere in the tracking bug, nor announced to QA in any way.

Aurora (Fx 30)

  • Feature sign-offs for the aurora merge will be done by Friday eod.

Nightly (Fx 31)

ESR (Fx 24.4)

Security

  • Working on some safe browsing stuff

Automation

  • Mozmill 2.0.6 on production now (skipped the test which is causing the flash crash)
  • We might not be able to run RC->Beta updates via CI for beta1 - an issue with optional parameters in parametrized jobs
  • TPS changes have been backported to Beta! Working on broken tests now
  • We will have two Automation Training days next week on Monday and Wednesday. Please join if you are interested in

Stability

  • Numbers of previous versions looked all good
  • 28 looks pretty normal except for bug 985428 (Trusteer Rapport crash)

Community

  • Responded to another 50 inquiries. (lizzard)


Previous Action Items

  • Add Softvision, Liz, Kamil, Nils, to desktop-qa list, switch to dev-quality
    • Done
  • mschifer to follow up with Platform/Automation re: WebGL automation coverage (so we can catch issues like bug 975824 more easily)

Discussion Items

  • QA whiteboard

https://bugzilla.mozilla.org/show_bug.cgi?id=978850

  • Criteria for selecting bugs to verify

Notes and Actions

  • QA whiteboard: Use current mechanism for existing bugs, and new QA whiteboard for new bugs that haven't been marked
  • Think about focusing our triage process; look at bugs that have been tagged by developers in platform, but ignore otherwise