Thunderbird:QA TestDay:2008-06-26
last week | index | next week »
Bug Day June 26, 2008
Schedule for Thursday at Bugdays page, which also tells you how to get started and get help.
Bug days are done to reduce the number of unconfirmed bugs in the bugzilla database, and to improve the quality of the bugs in the database.
Special Notice
Soon, bugs in Core: Mailnews: * will undergo a transformation - all will move to a new product, Mailnews Core. A major clean up of QA and Assignee will also be done, per draft proposal.
We mention this for two reasons: 1. Be advised you may get lots of bugmail during this process, 2. We need your help to do a manual triage of all severity=major+critical bugs. Two groupings:
- no comments after 2007-06-22 (26 bugs)
- has patch, no comments after 2007-06-22 (5 bugs)
For each bug:
- Can you reproduce the bug with a trunk build.
- Comments and/or update as needed, especially regarding any patches in progress, and determine what work still needs to be done
- Cc or assign any parties, particularly devs, who might be able to help push the bug forward
- If you don't close the bug, pick "Reassign bug to default" before committing changes so that QA and Assignee are reset to default
Focus
Let's drive these numbers down!
Focus for this bug day - suggested starting points:
- IMAP UNCOnfirmed (187 bugs)
- UNCOnfirmed, recent bugs with no responses (63 bugs)
- UNCOnfirmed :General (1) (153 bugs - unchanged for 60 days, created after 2007-08-01)
(1) If you can, move from General to another component, in addition to other triage action.
You may of course work on any bugs that interest you, including items in Bug queries or this variety pack of leftovers from prior bugdays:
- address autocomplete UNCO or changed<2007-06-22 (20 bugs) - compare to all autocomplete (43 bugs)
- UNCOnfirmed, severity=minor bugs (34 bugs)
- UNCO Crashers lacking formatted stack in summary (20 bugs - unchanged for 6 days)
- UNCO keyword=Dataloss (4 bugs - unchanged for 60 days)
Tips
Before starting, see the Bugdays page for information about what to do and how to get help. Don't be concerned if you don't understand everything, just ask for help.
Results
For this bugday, the times of the sessions, accounting for 30mins [1] of grace period before and after each session, were as follows:
- Session 1
- Start time: 2008-06-26 0530h PDT
- End time: 2008-06-26 0830h PDT
- Session 2
- Start time: 2008-06-26 1130h PDT
- End time: 2008-06-26 1430h PDT
- Session 3
- Start time: 2008-06-26 1830h PDT
- End time: 2008-06-26 2230h PDT
- 17 hour duration
- All sessions & intermediate rest time.
- Start time: 2008-06-26 0530h PDT
- End time: 2008-06-26 2230h PDT
| Sessions | Product | Any Change | Last bug day | Only Resolution Change [2] | Last bug day | ||
|---|---|---|---|---|---|---|---|
| Improvement | Improvement | ||||||
| Session 1 | Thunderbird-only | Q 28 | Q 77 | down (-17) | Q 15 | Q 31 | down (-7) |
| Core-only | Q 49 | Q 16 | |||||
| Session 2 | Thunderbird-only | Q 23 | Q 58 | down (-8) | Q 8 | Q 23 | up (+10) |
| Core-only | Q 35 | Q 15 | |||||
| Session 3 | Thunderbird-only | Q 9 | Q 21 | up (+8) | Q 2 | Q 6 | up (+4) |
| Core-only | Q 12 | Q 4 | |||||
| 17 hour Duration | Thunderbird-only | Q 76 | Q 205 | down (-5) | Q 27 | Q 71 | up (+10) |
| Core-only | Q 129 | Q 44 | |||||
Many thanks to volunteers and developers (total 5 - 10) who turned up for this bug day, and others that I may have possibly missed.
Notes:
- Spreadsheet of bugday results is compiled and updated after each session / bugday.
- The letter Q stands for the query with all the appropriate criteria, which over time may differ from the results that have been logged.
- [1] Session and period time includes 30mins before and after the official time period, so as to include early and late/spill over activity.
- [2] A resolution change may be non-terminal, for example a bug may have been reopened.
