Examples
Differences between revisions 6 and 7
|
Size: 1129
Comment: Added sample bug to the list.
|
Size: 1133
Comment: Fixed link to Bugs/Responses
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| * Due to lack of information, the bug also seemed to be more of a support request than a bug. I suspected that the problem was caused by a bad ISO download or an improper burn, which would fall under tech support rather than debugging. As such a combination of canned responses from Bugs/Responses was used (needs info and tech support). | * Due to lack of information, the bug also seemed to be more of a support request than a bug. I suspected that the problem was caused by a bad ISO download or an improper burn, which would fall under tech support rather than debugging. As such a combination of canned responses from ["Bugs/Responses"] was used (needs info and tech support). |
This page lists examples of bugs where the assignee and the bug triage team did a good job of clarifying the problem and identifying the actual bug.
If you see a nice example of good bug work, be sure to list it here.
Bugs
- Bug number, Link
- brief outline, of how the bug was processed
- remarkable aspects
- refer to ["Bugs/CommonTasks"] for tasks that are common
49175, [https://bugs.launchpad.net/distros/ubuntu/+source/ubiquity/+bug/49175 dapper install freeze at "loading kernel"]
- The end-user's bug report was very superficial and didn't include the necessary information. The bug was rejected with a "canned" message.
- Due to lack of information, the bug also seemed to be more of a support request than a bug. I suspected that the problem was caused by a bad ISO download or an improper burn, which would fall under tech support rather than debugging. As such a combination of canned responses from ["Bugs/Responses"] was used (needs info and tech support).
Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]
Bugs/Examples (last edited 2008-08-06 17:00:54 by localhost)