Bugs:Triage guide - Revision history

imported>ashley: convert some external links pointing to wiki.maemo.org to internal ones and swap freenode references to Libera instead

2021-11-09T09:33:30Z

convert some external links pointing to wiki.maemo.org to internal ones and swap freenode references to Libera instead

← Older revision	Revision as of 09:33, 9 November 2021
(No difference)

imported>ashley: convert some external links pointing to wiki.maemo.org to internal ones and swap freenode references to Libera instead

2021-11-09T09:33:30Z

convert some external links pointing to wiki.maemo.org to internal ones and swap freenode references to Libera instead

← Older revision		Revision as of 09:33, 9 November 2021
Line 6:		Line 6:

	# [https://bugs.maemo.org/createaccount.cgi Create an account.]		# [https://bugs.maemo.org/createaccount.cgi Create an account.]
	# Read the [~~https://wiki.maemo.org/index.php?title=~~Bugs:~~Stock_answers~~ Stock answers]. These stock responses are general examples of the kinds of comments that triagers should add to bug reports. There are even a surprising number of bug reports for which you can simply use these responses. Please always add a comment when changing the bug status to RESOLVED or adding the "moreinfo" keyword, so the user can comprehend your decision.		# Read the [[Bugs:Stock answers\|Stock answers]]. These stock responses are general examples of the kinds of comments that triagers should add to bug reports. There are even a surprising number of bug reports for which you can simply use these responses. Please always add a comment when changing the bug status to RESOLVED or adding the "moreinfo" keyword, so the user can comprehend your decision.
	# Find what should be changed. Read the [~~https://wiki.maemo.org/~~Bugs:~~Triage_guide~~#~~Steps_of_Triaging~~ Steps of Triaging] to determine what should be changed (if anything) and how.		# Find what should be changed. Read the [[Bugs:Triage guide#Steps of Triaging\|Steps of Triaging]] to determine what should be changed (if anything) and how.
	# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.		# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.
	# Ask someone to verify your changes. In #maemo-bugs on irc.~~freenode~~.~~net~~ mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").		# Ask someone to verify your changes. In #maemo-bugs on irc.libera.chat mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").

	As time goes by and you become more familiar with Bugzilla, please ask the [~~https://wiki.maemo.org/index.php?title=~~Bugsquad#Members Bugsquad members] to provide [http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.		As time goes by and you become more familiar with Bugzilla, please ask the [[Bugsquad#Members\|Bugsquad members]] to provide [http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.

	=== Potential tasks ===		=== Potential tasks ===

	Please take a look at [[Bugs:Tasks \| some ideas here]].		Please take a look at [[Bugs:Tasks\|some ideas here]].

	== Steps of Triaging ==		== Steps of Triaging ==
Line 43:		Line 43:

	Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should get the "moreinfo" keyword with a polite message, as should other things that are too ambiguous to be useful.		Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should get the "moreinfo" keyword with a polite message, as should other things that are too ambiguous to be useful.
	In many cases asking for a URL or attachment will help. If you need help making changes to bug fields ([http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers "editbugs"]), just comment describing what changes you want made, or ask for help from the #maemo-bugs channel on ~~Freenode~~ IRC (especially the bugmaster andre is good contact), or send an email to bugzilla@maemo.org.		In many cases asking for a URL or attachment will help. If you need help making changes to bug fields ([http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers "editbugs"]), just comment describing what changes you want made, or ask for help from the #maemo-bugs channel on Libera IRC (especially the bugmaster andre is good contact), or send an email to bugzilla@maemo.org.

	=== Is the bug a duplicate? ===		=== Is the bug a duplicate? ===
Line 70:		Line 70:
	* '''Crasher bugs'''		* '''Crasher bugs'''
	Should have Severity=Critical, Priority=High.		Should have Severity=Critical, Priority=High.
	Add the "moreinfo" keyword if they don't have a stack trace, and ask the reporter to get a decent stack trace (see ~~https://wiki.maemo.org/index.php?title=~~Bugs:~~Stock_answers~~ for more information). If there is no information about how it is triggered you should ask the original reporter how to reproduce the bug.		Add the "moreinfo" keyword if they don't have a stack trace, and ask the reporter to get a decent stack trace (see [[Bugs:Stock answers]] for more information). If there is no information about how it is triggered you should ask the original reporter how to reproduce the bug.
	* '''Something not working as expected'''		* '''Something not working as expected'''
	Severity=Low or Medium depending on how much it breaks the application.		Severity=Low or Medium depending on how much it breaks the application.
Line 92:		Line 92:

	Kudos to [http://browser.garage.maemo.org/news/8/ timeless], the [http://wiki.mozilla.org/MozillaQualityAssurance:Triage Mozilla Triage Team] and the [http://live.gnome.org/Bugsquad/TriageGuide GNOME Bugsquad]. I shamelessly copied huge parts from them.		Kudos to [http://browser.garage.maemo.org/news/8/ timeless], the [http://wiki.mozilla.org/MozillaQualityAssurance:Triage Mozilla Triage Team] and the [http://live.gnome.org/Bugsquad/TriageGuide GNOME Bugsquad]. I shamelessly copied huge parts from them.


	[[Category:Community]]		[[Category:Community]]

imported>andre: s/#maemo/#maemo-bugs

2010-10-22T17:17:02Z

s/#maemo/#maemo-bugs

← Older revision	Revision as of 17:17, 22 October 2010
(No difference)

imported>andre: s/#maemo/#maemo-bugs

2010-10-22T17:17:02Z

s/#maemo/#maemo-bugs

← Older revision		Revision as of 17:17, 22 October 2010
Line 9:		Line 9:
	# Find what should be changed. Read the [https://wiki.maemo.org/Bugs:Triage_guide#Steps_of_Triaging Steps of Triaging] to determine what should be changed (if anything) and how.		# Find what should be changed. Read the [https://wiki.maemo.org/Bugs:Triage_guide#Steps_of_Triaging Steps of Triaging] to determine what should be changed (if anything) and how.
	# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.		# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.
	# Ask someone to verify your changes. In #maemo on irc.freenode.net mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").		# Ask someone to verify your changes. In #maemo-bugs on irc.freenode.net mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").

	As time goes by and you become more familiar with Bugzilla, please ask the [https://wiki.maemo.org/index.php?title=Bugsquad#Members Bugsquad members] to provide [http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.		As time goes by and you become more familiar with Bugzilla, please ask the [https://wiki.maemo.org/index.php?title=Bugsquad#Members Bugsquad members] to provide [http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.
Line 43:		Line 43:

	Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should get the "moreinfo" keyword with a polite message, as should other things that are too ambiguous to be useful.		Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should get the "moreinfo" keyword with a polite message, as should other things that are too ambiguous to be useful.
	In many cases asking for a URL or attachment will help. If you need help making changes to bug fields ([http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers "editbugs"]), just comment describing what changes you want made, or ask for help from the #maemo channel on Freenode IRC (especially the bugmaster andre is good contact), or send an email to bugzilla@maemo.org.		In many cases asking for a URL or attachment will help. If you need help making changes to bug fields ([http://www.bugzilla.org/docs/2.22/html/useradmin.html#modifyusers "editbugs"]), just comment describing what changes you want made, or ask for help from the #maemo-bugs channel on Freenode IRC (especially the bugmaster andre is good contact), or send an email to bugzilla@maemo.org.

	=== Is the bug a duplicate? ===		=== Is the bug a duplicate? ===

imported>andre: /* Hardware problems and Hardware enhancement requests */

2010-09-01T11:37:44Z

Hardware problems and Hardware enhancement requests

← Older revision	Revision as of 11:37, 1 September 2010
(No difference)

imported>andre: /* Hardware problems and Hardware enhancement requests */

2010-09-01T11:37:44Z

Hardware problems and Hardware enhancement requests

← Older revision		Revision as of 11:37, 1 September 2010
Line 33:		Line 33:

	Maemo is a software platform, hence bug reports about hardware bugs are invalid in bugs.maemo.org. Please ask the reporter to either contact Nokia Care services via www.nokia.com or to contact the company who sold the product to them.		Maemo is a software platform, hence bug reports about hardware bugs are invalid in bugs.maemo.org. Please ask the reporter to either contact Nokia Care services via www.nokia.com or to contact the company who sold the product to them.
	If the report is about an enhancement idea for the hardware, please close the report as invalid and kindly ask the reporter to file a ticket in the [http://maemo.org/community/brainstorm/ Maemo Brainstorm] at http://maemo.org/community/brainstorm/ instead as hardware is out of scope for maemo.org Bugzilla.		If the report is about an enhancement idea for the hardware, please close the report as invalid and kindly ask the reporter to file a ticket in the [http://maemo.org/community/brainstorm/ Maemo Brainstorm] at http://maemo.org/community/brainstorm/ instead as hardware is out of scope for maemo.org Bugzilla. Also there is http://conversations.nokia.com/design-by-community/.

	==== Is it a valid, but wide and non-specific feature request? ====		==== Is it a valid, but wide and non-specific feature request? ====

imported>jukey: /* Acknowledgment */

2010-07-18T07:14:51Z

Acknowledgment

← Older revision	Revision as of 07:14, 18 July 2010
(No difference)

imported>jukey: /* Acknowledgment */

2010-07-18T07:14:51Z

Acknowledgment

← Older revision		Revision as of 07:14, 18 July 2010
Line 97:		Line 97:
	[[Category:maemo.org]]		[[Category:maemo.org]]
	[[Category:Bugzilla]]		[[Category:Bugzilla]]
			[[Category:Quality Assurance]]

imported>andre: /* Hardware problems and Hardware enhancement requests */

2010-02-17T12:24:25Z

Hardware problems and Hardware enhancement requests

← Older revision	Revision as of 12:24, 17 February 2010
(No difference)

imported>andre: /* Hardware problems and Hardware enhancement requests */

2010-02-17T12:24:25Z

Hardware problems and Hardware enhancement requests

← Older revision		Revision as of 12:24, 17 February 2010
Line 32:		Line 32:
	==== Hardware problems and Hardware enhancement requests ====		==== Hardware problems and Hardware enhancement requests ====

	Maemo is a software platform, hence bug reports about hardware bugs are invalid. Please ask the reporter to either contact Nokia Care services via www.nokia.com or to contact the company who sold the product to them.		Maemo is a software platform, hence bug reports about hardware bugs are invalid in bugs.maemo.org. Please ask the reporter to either contact Nokia Care services via www.nokia.com or to contact the company who sold the product to them.
	If the report is about an enhancement idea for the hardware, please close the report as invalid and kindly ask the reporter to file a ticket in the [http://maemo.org/community/brainstorm/ Maemo Brainstorm] instead as hardware is out of scope for maemo.org Bugzilla.		If the report is about an enhancement idea for the hardware, please close the report as invalid and kindly ask the reporter to file a ticket in the [http://maemo.org/community/brainstorm/ Maemo Brainstorm] at http://maemo.org/community/brainstorm/ instead as hardware is out of scope for maemo.org Bugzilla.

	==== Is it a valid, but wide and non-specific feature request? ====		==== Is it a valid, but wide and non-specific feature request? ====