Project specific, common debugging outputs definitions.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
When a bug is filed launchpad should list a series of steps for each project/package to produce common debugging outputs which the assignee/bug contact will/might require to fix the bug.. These could include crash reports, (where to find them for each project also).. It could include a series of common terminal commands, or a simple walk-through to get some sort of debugging information..
http://
Please see point 1 for an example of the information X.org packages would find useful, it will not always be useful, but it would be a base..
I feel this would speed up a fair number of reports from new comers to a project, who want to report the bug, but don't have an hour to find out which outputs are useful, then do them and then upload the results..
It would get out from people who can just describe the issue... Some individuals would ignore these steps, but surely it will lower workload a little overall..
Thanks, Alex Latchford.
| James Henstridge (jamesh) wrote | #1 |
Alex: I've marked your bug as a duplicate of bug 43893. There is now support for specifying bug reporting guidelines for projects, and the same should be made available for distribution packages in the near future.