Thunderbird:QA TestDay:2008-07-17

last week | index | next week »

Bug Day July 17, 2008

Schedule for Thursday at Bugdays page, which also tells you how to get started and get help.

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.

Special Notice

all Core: Mailnews: bugs will soon move to a new product, Mailnews Core. QA and Assignee will also be cleaned up. 1. You may get lots of bugmail in this process, 2. Please help triage these severity=major+critical bugs (no comments after 2007-06-22 - 21 bugs)

For each bug:

1. Can you reproduce the bug with a trunk build?
2. Comment, especially regarding patches in progress and work still needed.
3. Cc or assign any parties, particularly devs, who might help push the bug forward
4. If not closing, pick "Reassign bug to default" before commit to reset QA and Assignee to default

Focus

Let's drive these numbers down!

Focus for this bug day - suggested starting points:

• trunk/TB3 UNCOnfirmed bugs with no recent activity (62 bugs)
• other (mostly TB2) UNCOnfirmed & no comments, no recent activity (89 bugs)

Of course you may work any bugs that interest you, perhaps from Bug queries, or this variety pack from prior bugdays:

• IMAP UNCOnfirmed (150 bugs)
• UNCOnfirmed, very recent bugs with no responses (86 bugs)
• UNCOnfirmed :General (1) (150 bugs - unchanged >60 days, created after 2007-08-01)
  (1) Move bug from General to another component if possible, in addition to other triage action.
• address autocomplete UNCO or changed<2007-06-22 (18 bugs) - vs all autocomplete (40 bugs)
• UNCOnfirmed, severity=minor bugs (35 bugs)
• UNCO Crashers lacking formatted stack in summary (23 bugs - unchanged for 6 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-07-17 0530h PDT
  • End time: 2008-07-17 0830h PDT

• Session 2
  • Start time: 2008-07-17 1130h PDT
  • End time: 2008-07-17 1430h PDT

• Session 3
  • Start time: 2008-07-17 1830h PDT
  • End time: 2008-07-17 2230h PDT

• 17 hour duration
  • All sessions & intermediate rest time.
  • Start time: 2008-07-17 0530h PDT
  • End time: 2008-07-17 2230h PDT

Bug Day results

Sessions	Product	Any Change		Last bug day	Only Resolution Change [2]		Last bug day
				Improvement			Improvement
Session 1	Thunderbird-only	Q 10	Q 22	down (-88)	Q 4	Q 11	down (-50)
	Core-only	Q 12			Q 7
Session 2	Thunderbird-only	Q 13	Q 20	down (-36)	Q 1	Q 1	down (-13)
	Core-only	Q 7			Q 0
Session 3	Thunderbird-only	Q 5	Q 8	up (+2)	Q 3	Q 3	up (+3)
	Core-only	Q 3			Q 0
17 hour Duration	Thunderbird-only	Q 50	Q 85	down (-101)	Q 12	Q 21	down (-59)
	Core-only	Q 35			Q 9

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.