Bugs: Difference between revisions
| Line 11: | Line 11: | ||
Try to avoid endless discussions why a bug was introduced, be polite! | Try to avoid endless discussions why a bug was introduced, be polite! | ||
Keep in mind, devs often don't read the forum, they've | Keep in mind, devs often don't read the forum, they've few time for it. | ||
If you want more tips for a good bug-report, please read "[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]" | If you want more tips for a good bug-report, please read "[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]" | ||
Revision as of 12:08, 8 February 2011
How to report bugs
Before filling a bug, please look if someone else already has reported this issue.
To report a bug, please give a description, what is going wrong and how it can be reproduced. what steps are required to reproduce it?
Nearly always attach infolog.txt, as it contains system/driver/version info and if spring crashed, it also (should) contain an crashdump, which allows to find out, why it crashed and to fix it. If it makes sense, make a screenshot + attach it.
The better the bug-report, the better the chances, that it is fixed!
Try to avoid endless discussions why a bug was introduced, be polite!
Keep in mind, devs often don't read the forum, they've few time for it.
If you want more tips for a good bug-report, please read "How to Report Bugs Effectively"
