QA/SoftVision/Meetings/Desktop:2014-05-07
From MozillaWiki
< QA | SoftVision | Meetings
Contents
Desktop QA Standup - May 7th, 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-04-30
Attendees: Paul, Mihaela, Petruta, Catalin, Anthony, Henrik, Tracy, KaiRo, Juan, Marc, Matt, Kamil, Andrei, Bogdan, Otilia, lizzard, Cornel
Heads-Up
- Upcoming PTOs:
- Florin - PTO - May 5-16 (please contact Otilia or the team in my absence)
- KaiRo off from after this mtg until the weekend (local conference), back 5/12
- juanb - PTO - May 21-26
- mwobensmith May 9th
- lizzard May 22-26 (PTO for 22/23)
- Events
- This Friday - Firefox 30 Beta 3 testday https://etherpad.mozilla.org/testday-20140509
Upcoming Schedule
- Fx29.0.1: Friday, May 9th
Previous Action Items
- Clear etherpad after notes are posted to the wiki.
Discussion Items
[ashughes] Iteration Development planning process improvements
- Marco will support what we come up with if we define it
- Reducing the volume of [qa?] triage
- What criteria could define "automatic" [qa+] or [qa-] to reduce the volume of [qa?] incoming
- ie. we tend not to test [UX] and [Breakdown] bugs -- these could be auto [qa-]
- small polish, breakdown, test-only
- we should still vet [qa-] once per iteration
- What criteria could define "automatic" [qa+] or [qa-] to reduce the volume of [qa?] incoming
- Handling of landings which occur too close to migration day
- Should we have a cut-off date? (ie. Thursday before migration)
- Nope, let it ride
- Should changes not QA'd in time be backed out before migration? or backed out post-migration *if* issues are found?
- let changes ride and back out if problems are found
- high-risk changes should be treated similar to uplifts (approved/denied by RelMan)
- Should we have a cut-off date? (ie. Thursday before migration)
- Do we feel like our attendance to the Tuesday meeting is valued and a good use of our time?
- may be opportunity to raise questions in the meeting about QAing bugs from the backlog sent out before the meeting
- we should revisit this in a few weeks after Juan's had a chance to go through the process
- Feature Owners should inform Automation when they notice UI changes in their bugs
- CC Henrik Skupin using the in-qa-testsuite flag
Channel Status
Beta (Fx 30) (Tracy/KaiRo)
Aurora (Fx 31) (Anthony/Liz)
- Updates were re-enabled last Friday
- No major concerns at this time
Nightly (Fx 32) (Juan/Kamil)
- Major source of instability now fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1005646
ESR (Fx 24.5)
Security
- safe browsing in Fx30
- ongoing testing of mozilla::pkix for Fx31
- key pinning landed in Fx32
Automation
- General
- Currently setting up our priorized project documentations: https://wiki.mozilla.org/QA/Automation#Projects
- Next Automation Training day is targeted for Wednesday, May 21st
- Mozmill
- The massive jsbridge disconnect issues seem to be gone since we increased the delay for the addon installation dialog. It still needs to be fully investigated
- Working with RelEng on Pulse update notifications (see bug 735184)
- TPS
- All TPS tests are passing locally - not sure why on our CI some tests are failing. Actually the machine seems to be very fragile and broken for a couple of services like VNC. So it may be related. We might want to get the new system setup as soon as possible. Where should this be?
Stability
- Some trunk issues caused churn, but generally we look good
- Beta is a bit on the high side due to bug 1002748 and bug 988311, which will both be fixed by DLL blocklisting, no large regressions so far other than those.
- Will do more in-depth beta regressions comparisons next week.
Community
- One and Done project is about to start adding features
- project Baloo data process continues (bug triage, Services, Moztrap)
- updated the incoming / UNCO triage pages for Nightly, Aurora, Beta, and Release
Notes and Actions
- Notify automation team when significant UI changes are about to happen.
- How do we notify other than cc'ing whimboo?: qa-testsuite flag