QA/SoftVision/Meetings/Desktop:2014-05-21
From MozillaWiki
< QA | SoftVision | Meetings
Contents
Desktop QA Standup - May 21st, 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-05-14
Attendees: tracy, Matt, Juan, Marc, Mihaela, Kamil, Bogdan, Florin, Francesca, Maja, Nils, Paul, Petruta, Catalin, Liz, KaiRo
Heads-Up
- Upcoming PTOs:
- juanb - PTO - May 21-26
- lizzard May 22-26 (PTO for 22/23)
- Cornel - May 23
- Catalin - May 26-30
- Events
- Firefox 30 Beta 7 Testday - Friday, May 23rd
Upcoming Schedule
Previous Action Items
- root cause project, list of areas, some numbers
- absence of qa flag means qa?; qa+/- happening during iteration triage, getting better
- need to finalize which tags/flags we will use so we can communicate them broadly and start using them
- thoughts on "root cause" project (https://docs.google.com/document/d/16OVgqQxsjMVpOHcAQ7B5py4BpahiEL24q6oo5pZy_bs/edit )
- looking at reopened bugs + regressions, by component, in Core + Firefox (lizzard)
- interested to see if there are particular hot spots where we might focus more QA attention.
- should probably focus on Core -- I suspect "big" components like JS Engine and Graphics need better attention -- in particular we have next to no regression coverage for WebGL -- Firefox probably has good coverage given all teams are on the Iterative Development process now (ashughes)
- template for bug investigation: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Au-Dw_f8snrydDhseUczVFY0Z2pmSnMwc2JYdG5McEE&usp=sharing#gid=0
- iterative development process (ashughes)
- engineering seems to have bought in to setting qa+/- as part of the planning/work selection process when the answer is known -- this should help ease the triage burden and noise in bugzilla
[clint-thought] - we could let engineering continue setting that in the QA whiteboard and then translate that into keywords or what-have you. (Just because it's hard to change people's habits it might be easier to do this than try to change them). - My two cents.
- we'll still have qa? bugs for the meantime but how do people feel about deprecating that as a catch-all, use it as an uncertainty flag -- anything without a qa tag with an iteration tag would essentially act as our funnel +1
Discussion Items
- Firefox QA reorg
Channel Status
Beta (Fx 30) (Tracy/KaiRo)
- beta6 was delayed a day due to late landings. I'll be sending push to release shortly.
Aurora (Fx 31) (Anthony/Liz)
Nightly (Fx 32) (Juan/Kamil)
ESR (Fx 24.6)
Security
More pkix testing, cert pinning, root cert removal project
Automation
Stability
- 29 release is slightly worse than 28 apparently, crash rate increase in the ~5% range
- 30 beta is worse than 29 so far, but some fixed crashes need to be weeded out by updates still, including bug 1002748 and bug 1009624, and we have two top-10 regressions in plugin shutdown: bug 883134 and bug 1013972.
Community
Notes and Actions
- KaiRo - check with telemetry about shutdown hangs
- KaiRo - post about keywords.