QA/SoftVision/Meetings/Desktop:2014-03-26
From MozillaWiki
< QA | SoftVision | Meetings
Desktop QA Standup - March 26th, 2014
Dial-in Information
- Wednesdays, 8:30am Pacific Time
- Telephone:
- 650-903-0800 or 650-215-1282 x92 Conf# 99779 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 99779 (US)
- Vidyo Room: QA-Desktop
- Vidyo Guest URL
- Agenda and notes: etherpad
- Archives: wiki.mozilla.org
- Previous Meeting: https://wiki.mozilla.org/QA/SoftVision/Meetings/Desktop:2014-03-19
Attendees: Manuela, Paul, Ioana, Tracy, KaiRo, Petruta, Mihaela, Camelia, Florin, Anthony, Matt,VarCat, Juan, Marc, Bogdan, Kamil
Heads-Up
- Upcoming PTOs:
- Events
- Firefox 29.0 Beta 3 Testday - Friday, March 28th
- New team members.
Upcoming Schedule
Channel Status
Beta (Fx 29)
Aurora (Fx 30)
Nightly (Fx 31)
ESR (Fx 24.4)
Security
- mozilla::pkix compatiblity
- Removing 1024bit root certs
- Safe browsing
Automation
Stability
- numbers look good, still waiting to be able to push blog post on stability program
Community
Previous Action Items
- mschifer to follow up with Platform/Automation re: WebGL automation coverage (so we can catch issues like bug 975824 more easily)
- Think about focusing our triage process; look at bugs that have been tagged by developers in platform, but ignore otherwise
Discussion Items
- Firefox 28 post-mortem: https://mozqa.etherpad.mozilla.org/firefox28-post-mortem
- Nightly-only resources: does this still make sense given the new development process?
- Can we move the discussion items to the top of the meeting?
- Meeting invite still refers to PB&J as the meeting room
- Bugs to select for verification - proposal mentioned last time: any bugs out of the Firefox iteration list + anything marked qa+ or qa? (or verifyme?) in Firefox/Toolkit/Core products (and marked with the appropriate target milestone)
- What do people think about that?
- Until the whole Firefox desktop team is on iterations, will actually have to have first part as "any bugs fixed in iteration or Firefox product marked with that target milestone"
- We usually already miss most of the Toolkit/Core bugs and the vast majority of those would be qa- so it's probably better to not triage all of those but concentrate on those that get flagged as needing us.
- If we go with that, we need to heavily communicate this to developers so qa+/? actually get set where needed
Notes and Actions
- WebGL test suties available, not kept up/disabled, Marc to talk to them about how we can help them.
- Safe browsing: Matt to investigate history of feature, what goes into Fx29, what is in test suite, how to cover in test day
- Moving disscussion items/previous action items to the top. Marc to change meeting invitation (PBJ -> ?).
- Where are we with keywords and qa whiteboard tags.
- [Kairo] Send out a summary to dev-quality and dev-planning and elicit discussion.