Thunderbird:QA TestDay:2008-08-28
last week | index | next week »
Bug Day August 28, 2008
How to get help, how to get started, and schedule for Bugdays.
Bug days are conducted to reduce the number of UNCOnfirmed bugs in the bugzilla database, and to improve the quality of the bugs in the database.
Focus
Let's help our bug reporters by driving these numbers down!
Focus for this bug day is a fresh departure from previous bugdays, namely Patch Love . Over 200 bugs have patches that may need assistance or advice to help get the patch landed. And we would like to see as many as possible get into Thunderbird 3. Patch Love outlines a process you can use to triage and assist such bugs. We focus this week on two queries. A suggested approach is sort the resulting query by component, and then work on bugs whose components you best understand or most care about:
- Bugs that require string changes and will affect localizers (53 bugs)
- Bugs with activity within last 800 days (127 bugs)
If you prefer to work unconfirmed bugs:
- trunk/TB3 UNCOnfirmed bugs with no recent activity (65 bugs)
- other (mostly TB2) UNCOnfirmed & no comments, no recent activity (53 bugs)
Of course, work any bugs that interest you, perhaps from Bug queries or a variety from prior bugdays:
- offline/online bugs with no comment since 2007-07-31 (7 bugs) or, less selective triage confirmed and unconfirmed offline (66 bugs) ... these bugs are especially important to new features coming in to Thunderbird 3 which rely on offline/online functionality. as hardcoded bug#s
- IMAP UNCOnfirmed (125 bugs)
- UNCOnfirmed, very recent bugs with no responses (108 bugs)
- UNCOnfirmed component=:General (1) (177 bugs)
(1) Move bug from General to another component if possible, in addition to other triage action. - address autocomplete UNCO or changed<2007-06-22 (14 bugs) - vs all autocomplete (21 bugs)
- UNCOnfirmed, severity=minor bugs (36 bugs)
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-08-28 0530h PDT
- End time: 2008-08-28 0830h PDT
- Session 2
- Start time: 2008-08-28 1130h PDT
- End time: 2008-08-28 1430h PDT
- Session 3
- Start time: 2008-08-28 1830h PDT
- End time: 2008-08-28 2230h PDT
- 17 hour duration
- All sessions & intermediate rest time.
- Start time: 2008-08-28 0530h PDT
- End time: 2008-08-28 2230h PDT
| Sessions | Product | Any Change | Last bug day | Only Resolution Change [2] | Last bug day | ||
|---|---|---|---|---|---|---|---|
| Improvement | Improvement | ||||||
| Session 1 | Thunderbird-only | Q 193 | Q 205 | up (+116) | Q 175 | Q 178 | up (+102) |
| Core-only | Q 12 | Q 3 | |||||
| Session 2 | Thunderbird-only | Q 519 | Q 536 | up (+452) | Q 23 | Q 23 | up (+18) |
| Core-only | Q 17 | Q 0 | |||||
| Session 3 | Thunderbird-only | Q 37 | Q 40 | up (+26) | Q 8 | Q 8 | up (+1) |
| Core-only | Q 3 | Q 0 | |||||
| 17 hour Duration | Thunderbird-only | Q 2677 | Q 2803 | up (+2,524) | Q 220 | Q 227 | up (+126) |
| Core-only | Q 126 | Q 7 | |||||
NOTE: 2604 bugs were mass-changed by dmose during the course of this bugday, as they were mass-reassigned back to nobody@mozilla.org . Final figure logged in Google Docs is thus 2803 - 2604 = 199.
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.
