Thunderbird:Bugdays: Difference between revisions

You might also visit [[Thunderbird:Bugdays_Planning|Planning for bugdays]], and other [[Thunderbird|Thunderbird wiki pages]] for information about the state of Thunderbird, planning, and ways you can help and provide feedback.

In contributing to improving Thunderbird's quality, you will feel that the program you use daily is a bit yours. Rub elbows with new and experienced contributors as you take a break from your boring everyday routine. Anyone can participate and be a valuable contributor - no coding and no experience required. The information below will help you get started, and people are available to assist you.

Resolving bugs is the goal. To do that, some first need cleaning, and there are lots (LOTS!) of bugs:  

* some might not be real bugs and need confirmation

Bugdays are help newcomers join with experienced people in cleaning up the database and [https://bugzilla.mozilla.org/reports.cgi?product=Thunderbird&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A&datasets=UNCONFIRMED%3A drive down the red (UNCONFIRMED) line in this chart].  [https://bugzilla.mozilla.org/chart.cgi?category=-All-&subcategory=-All-&name=1183&label0=All+UNCONFIRMED+bugs&line0=1470&label1=UNCO+excl.+enh+%26+created+before+2007-04-07&line1=1472&label2=UNCONFIRMED+excl.+enhancements&line2=1471&datefrom=2008-03-20&dateto=&action-wrap=Chart+This+List another chart view]

Staffed sessions allow you to participate, day or evening, at any location in the world.  Attend all sessions, or just part of one. If you can't attend a scheduled session just drop in between sessions - someone might be hanging out who can help you. If you can't participate today, we invite you to [[Thunderbird:QA_Days|participate in a future bugday]]. Or work on any bug any day or time - see [[Thunderbird:Bugdays#Where|Where]] about getting help.

* Searching in bugzilla can be tricky. [https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html Quicksearch tricks] and [https://bugzilla.mozilla.org/query.cgi Advanced Search] can be used to develop more accurate search results.

# '''Get a build''' - Testing is best done with [http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/ nightly trunk builds] - trunk is where Thunderbird 3 is currently in development and it has all the latest fixes. If you cannot use trunk, please make sure you use the [http://www.getthunderbird.com/ latest update of Thunderbird version 3].   

# '''Work bugs''' - For UNCONFIRMED bugs, you should attempt to replicate the problem specified in the bug report, and mark as "confirmed" if you are able to replicate '''and''' the steps to reproduce are well documented and easily followed '''and''' the problem exists in trunk build. If you are not running trunk but can replicate with current release, please comment but do not confirm. If you are running trunk and cannot replicate, you might close it dupe, WFM, INVALID, or perhaps the issue is not easily reproduced.<p>Other helpful steps include:

#* Clarify bug reports without distorting or changing the original problem.

#* Change the summary to be more accurate to the problem being reported, and if appropriate remove words so summary is less chatty - a bug should not read like a book

#* Close bug reports as [https://bugzilla.mozilla.org/page.cgi?id=fields.html#status WORKSFORME, INVALID, or INCOMPLETE] when it's appropriate to do so (see [https://bugzilla.mozilla.org/page.cgi?id=fields.html#status status descriptions ] to find out what is appropriate).

#* Ask bug reporter in a bug comment to provide missing information that will help to replicate and ultimately fix the bugs they report.

#* Remember to cite what version(s) of Thunderbird you are using.