CommonTasks
|
Size: 2867
Comment:
|
Size: 3269
Comment: edits
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| * you made sure, that the bug doesn't occur because of Ubuntu related changes * the change too hard to fix for yourself and anyone else in the team |
* you made sure that the bug doesn't occur because of Ubuntu related changes, * the change is too hard to be fixed by yourself or anyone else in the team. |
| Line 12: | Line 12: |
| * include all the necessary information, like * how to reproduce * which version is used (which version of dependend libraries, if the bug indicates problems there) |
* include all the necessary information, such as * how to reproduce the bug * which version is used (which version of dependent libraries, if the bug indicates problems there) |
| Line 16: | Line 16: |
| * where the whole conversation is to be found | * where the whole conversation can be found |
| Line 21: | Line 21: |
| If you feel that the bug reported is a feature request disguised as a bug report, please introduce the reporter gently to the Specification Process we have. Be sure to mention ["SpecTemplate"] and http://launchpad.net/specs | If you feel that the bug reported is a feature request disguised as a bug report, please introduce the reporter gently to the Specification Process we have. Be sure to mention the following specification resources; FeatureSpecifications, SpecSpec, ["SpecTemplate"] and http://launchpad.net/specs |
| Line 31: | Line 31: |
| If you feel that the bug reported is a suggestions for changing defaults disguised as a bug report, please kindly reroute the discussion to a mailing list or a discussion forum. | If you feel that the bug reported is a suggestions for changing defaults disguised as a bug report, please kindly reroute the discussion to an appropriate mailing list or a discussion forum. If this has already been discussed and rejected, explain the reasons to the user and direct them to the corresponding discussion for further suggestions/comments. |
| Line 36: | Line 36: |
| Finding Duplicates of bugs is a very valuable contribution in the Bug community. Users sometimes don't know, how to check if the same bug was already filed, and sometimes don't care. To weed out simple '''ME TOO''' messages and aggregate information in one place is crucial in the process of fixing a bug. | Finding duplicates of bugs is a very valuable contribution in the Bug community. Users sometimes don't know how to check if the same bug has already been filed, and sometimes they don't care. Weeding out simple '''ME TOO''' messages and aggregating information in one place is crucial to the process of fixing a bug. |
| Line 38: | Line 38: |
| There are quite some measures you can take to help out with this specifically. Look up bugs for the same component. Try to rephrase your search concentrate on ''actions'' an ''words that describe'' the items involved to reproduce this crash. |
There are quite a few measures you can take to assist with this aspect, one way is to search for bugs filed for the same component, also try to rephrase your search, and concentrate on ''actions'' and ''words that describe'' the items involved to reproduce this crash. |
| Line 47: | Line 45: |
| * Hard ones: | * MOre difficult ones: |
| Line 51: | Line 49: |
| If you can't find it in the list of open bugs, you could try to find it in the list of closed ones. Don't feel discouraged, if you don't find duplicates fast in the beginning, after some time you will know the usual suspects. | If you can't find it in the list of open bugs, you could try to find it in the list of closed ones. Don't feel discouraged, if you don't find duplicates fast in the beginning, after some time you will get to know the usual suspects, and learn how to more easily identify them. |
| Line 53: | Line 51: |
| == Reminding of the Code of Conduct == | == Reminder of the Code of Conduct == |
| Line 55: | Line 53: |
| The Code of Conduct applies to conversations in bug reports too. So if you observer people not being respectful, please point them to http://www.ubuntulinux.org/community/conduct/document_view | Note that the Code of Conduct applies to conversations in bug reports too. So if you observe people being disrespectful, please direct them to http://www.ubuntulinux.org/community/conduct/document_view ---- Back to HelpingWithBugs |
Overview
Forwarding bugs upstream
You can forward bugs to the authors of the software (upstream), if
- you made sure that the bug doesn't occur because of Ubuntu related changes,
- the change is too hard to be fixed by yourself or anyone else in the team.
If you do this, be sure to
- include all the necessary information, such as
- how to reproduce the bug
- which version is used (which version of dependent libraries, if the bug indicates problems there)
- who reported it
- where the whole conversation can be found
- create a bug watch in Malone for this
How to Deal with Feature Requests
If you feel that the bug reported is a feature request disguised as a bug report, please introduce the reporter gently to the Specification Process we have. Be sure to mention the following specification resources; FeatureSpecifications, SpecSpec, ["SpecTemplate"] and http://launchpad.net/specs
How to deal with Support Requests
If you feel that the bug reported is a support request disguised as a bug report, please introduce the reporter gently to the Support Tracker we have. Be sure to mention http://launchpad.net/support
How to deal with suggestions for changing defaults
If you feel that the bug reported is a suggestions for changing defaults disguised as a bug report, please kindly reroute the discussion to an appropriate mailing list or a discussion forum. If this has already been discussed and rejected, explain the reasons to the user and direct them to the corresponding discussion for further suggestions/comments.
Finding Duplicates
Finding duplicates of bugs is a very valuable contribution in the Bug community. Users sometimes don't know how to check if the same bug has already been filed, and sometimes they don't care. Weeding out simple ME TOO messages and aggregating information in one place is crucial to the process of fixing a bug.
There are quite a few measures you can take to assist with this aspect, one way is to search for bugs filed for the same component, also try to rephrase your search, and concentrate on actions and words that describe the items involved to reproduce this crash.
Examples:
- Easy ones:
[http://bugzilla.ubuntu.com/show_bug.cgi?id=18808 DAAP support] is a duplicate of
[http://bugzilla.ubuntu.com/show_bug.cgi?id=18733 please enable daap]
- MOre difficult ones:
[http://bugzilla.ubuntu.com/show_bug.cgi?id=17858 plug:spdif on emu10k1 gone after breezy upgrade] is a duplicate of
[http://bugzilla.ubuntu.com/show_bug.cgi?id=15585 Muted sound after dist-upgrade from Hoary to Breezy]
If you can't find it in the list of open bugs, you could try to find it in the list of closed ones. Don't feel discouraged, if you don't find duplicates fast in the beginning, after some time you will get to know the usual suspects, and learn how to more easily identify them.
Reminder of the Code of Conduct
Note that the Code of Conduct applies to conversations in bug reports too. So if you observe people being disrespectful, please direct them to http://www.ubuntulinux.org/community/conduct/document_view
Back to HelpingWithBugs
Bugs/CommonTasks (last edited 2011-06-15 18:35:14 by c-98-246-63-231)