QA/Meetings/2015/October 14

=Prep=

= Agenda + Minutes =

 Minutes:

Content from the meeting itself ("the minutes") will be displayed in blue boxes like this.

Before we Start
A few minutes before we officially start, we'll try to have a few people in the IRC channel:
 * QA/IRC

IRC Minutes
We'll touch on a few metrics such as UNCONFIRMED bug count and regressions, and then we'll have each person in the meeting bring up whatever QA topics they'd like to address.

Some people like the current meeting time on Wednesdays, but if there's enough interest in change, we'll do it.

Stats
(we'll just discuss stats in the meeting)

Bugs/Topics to discuss
Pending topics:
 * State of multimedia in macOS All The Computers
 * Specifically: Have we finished image testing yet?
 * Oct 07 (Robinson) -> Yes, image testing is finally done! (See completed ACTION item below)
 * ACTION Items:
 * ACTION: File an enhancement request for a script that normalizes and diffs two user profiles (mjayfrancis)
 * ACTION: Review MABs, wiki pages and other resources dependent on them, and determine workload to switch over to using Priority:highest (Robinson or Other)
 * Oct 7 - (Robinson) - Reviewed (mab4.3, mab4.4, mab5.0) and verified that all listed bugs were highest-Priority (and vice-versa). We can now close these MAB tracker-bugs at our convenience.
 * ACTION: Design better plan for recruiting and retaining volunteers for QA Team (Robinson)
 * ACTION: Make a simple page of things new QA should be aware of (jphilipz)


 * Halloween Bug Hunting Session: BugHunting_Session_5.1.0.0

COMPLETED ACTION ITEMS

 * [DONE] ACTION: steve-_- will work on finishing the baseline image media support tests for macOS
 * Oct 07 - (Robinson) - Final tests for macOS performed; Windows test results clarified; all test results aggregated on Summary page.


 * [DONE] ACTION: Formulate patch proposal to put 'needsPrioritizing', 'needsRegressionTesting', etc.. tags into Whiteboard (Robinson)
 * Oct 14 - Robinson - Create patch
 * Oct 16 - Robinson - Improve patch and test; does this strategy help us to encourage good habits when triaging bugs?

New topics

 * Team members busy this week => full meeting next week
 * First round of testing of whiteboard patch on Bugzilla-test VM