QA/Community/Bug Day: Difference between revisions

m
no edit summary
mNo edit summary
Line 15: Line 15:
** etc.
** etc.
* Week 2 (March 27th, 2007) - We'll map the issues discovered in week one to open bugs or file new bugs as necessary.
* Week 2 (March 27th, 2007) - We'll map the issues discovered in week one to open bugs or file new bugs as necessary.
= Getting Started =
While the topic of day may have a particular focus for the session, we always want to try to do the following:
* Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
* Clarify bug reports whenever we can do so without distorting the problems.
* Close bug reports as WORKSFORME or INVALID when it's appropriate to do so.
* Ask reporters to provide missing information that would help to replicate and ultimately fix the bugs they report.
''Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.''


= Schedule =
= Schedule =
Line 114: Line 103:


'''Where do I start?'''
'''Where do I start?'''
While the topic of day may have a particular focus for the session, we always want to try to do the following:
* Replicate the problems specified in bug reports and mark them as "confirmed" whenever we are able to do so.
* Clarify bug reports whenever we can do so without distorting the problems.
* Close bug reports as WORKSFORME or INVALID when it's appropriate to do so.
* Ask reporters to provide missing information that would help to replicate and ultimately fix the bugs they report.
''Note: If you don't have the necessary rights to make a change to a bug, add a comment to the bug detailing what should be changed and why. You can also make this known in the #bugday channel, and one of the moderators or an experienced volunteer will assist you.''
* The following documentation is good to become familiar with for anyone working on Mozilla projects:
* The following documentation is good to become familiar with for anyone working on Mozilla projects:
** [http://www.mozilla.org/quality/ Mozilla QA] linked to from the "For Testers" section of [http://www.mozilla.org/developer/ mozilla.org/developer]
** [http://www.mozilla.org/quality/ Mozilla QA] linked to from the "For Testers" section of [http://www.mozilla.org/developer/ mozilla.org/developer]
Line 133: Line 131:
* [http://www.mozillazine.org/talkback.html?article=954 Asa's "Original" Bug Day post]
* [http://www.mozillazine.org/talkback.html?article=954 Asa's "Original" Bug Day post]
* [http://weblogs.mozillazine.org/qa/archives/2006/04/bug_day_revival_starts_may_2_2.html Tracy's "Bug Day Revival" QA Blog post]
* [http://weblogs.mozillazine.org/qa/archives/2006/04/bug_day_revival_starts_may_2_2.html Tracy's "Bug Day Revival" QA Blog post]
*[http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Archive Archive of bugday topics]
Confirmed users
4,072

edits