Discussion Items

Personal Q4 Goals
- If you havent filled out your individual Q4 goals (or made final tweaks), please do so this week. [you know who you are!] Remember, your goals should reflect that of the QA All and Team Execution Goals listed at the top

Current Priorities check
1. Crashes. The no.1 priority is Firefox crash investigation
2. Fx 1.9.1.4 testing. There are 142 fixed bugs, with 78 that need verification for this release. Al and team is overwhelmed, so please assist with verifications as much as you can. This is going to affect the current user set, so we need to make sure the top bugs at least are not regressing
3. Fennec & 3.6 work. We need to keep pushing hard on testing features and solidifying the betas before we ship. But the top 2 come first if you have to *# Your other work you have. Put them on a temporary backseat if you can.

VERIFIED keyword? (tchung, aakash)
- See discussion thread in mdq
- What's the best usage of qa's time when verifying bugs? What is the rate of reopening a bug? Should we just stick to branch only?

Project Updates

Firefox 3.6 (juanb)
- code freeze tonight (very subject to change)
  - We must try to get any litmus tests for new features done as soon as possible, in order to guide volunteers to test.
  - Create test cases as you go through your feature verifications. Tests don't have to be completely fleshed out, for now.
  - Try to complete test plans; update completion percentage numbers.

QA Metrics ( Murali )
- Created bug fixes trend by developer / by group and added it to the dashboard.
  - These reports would show the number of blocker/non-blocker bugs fixed by developer in the last 24 weeks.
- Creating a "Details of Comments made by Engineer" in BugZilla in the last 30 days reports section this week.