689
edits
Changes
From SME Server
Jump to navigationJump to searchSME Server:Documentation:QA:Bugtracker (view source)
Revision as of 00:39, 15 September 2012
, 00:39, 15 September 2012Added to a new categorisation page for SME Server project pages
<noinclude>{{Incomplete}}</noinclude>
<noinclude>{{Incomplete}}</noinclude>
The bug tracker is the spider in the web of our development as we use it to document new feature requests and issues with the current code base of SME Server. Problems are investigated, solutions discussed and testing of fixes is documented in it.
The bug tracker is the spider in the web of our development as we use it to document new feature requests and issues with the current code base of SME Server. Problems are investigated, solutions discussed and testing of fixes is documented in it.
Although it might seem daunting to use it at first, once you get used to it, is not much harder than for instance the forums.
Although it might seem daunting to use it at first, once you get used to it, is not much harder than for instance the forums.
===Reporting a bug===
===Reporting a bug===
{{Note box|Please keep in mind the your problem might be very pressing to you, but since we live all over the world and do development and support in our spare time, you will have to have some patients. The goal of the bugtracker is to properly investigate the issue, which means gathering information and as much details as required. Do '''not''' expect your problem to be fixed immediately, the bugtracker is not a support platform.}}
In the previous section a few hints were given already on actions to do when reporting a bug or feature request. Users reporting bugs to us are valuable, but the quality of the bug reports is also important to us, in order to address the raised issue as good as we can.
In the previous section a few hints were given already on actions to do when reporting a bug or feature request. Users reporting bugs to us are valuable, but the quality of the bug reports is also important to us, in order to address the raised issue as good as we can.
We therefore kindly ask you to read the contents of [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html "How to report bugs effectively"] as it will give you a very good idea of how we like you to report our bugs so we can diagnose and where required, fix them as adequately as possible.
We therefore kindly ask you to read the contents of [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html "How to report bugs effectively"] as it will give you a very good idea of how we like you to report our bugs so we can diagnose and where required, fix them as adequately as possible.
* No bug is too trivial to report - small bugs may hide big bugs
* No bug is too trivial to report - small bugs may hide big bugs
* Clearly separate fact from speculation
* Clearly separate fact from speculation
Please fill in the form as precise as you can. Specify a accurate summary that describes your issue as descriptive as possible, yet shortly. In the comment field please specify the details on your setup as well as on the problem. Make sure you specify error messages exactly as you see them and do not paraphrase them. Don't elaborate too much, but make sure you are not too brief either.
Generally a food bug report would answer the following questions:
What is the history of your server?
What are you expecting to happen?
What is actually happening?
What did you do that triggered the issue or might have lead to it appearing?
[[Category:SME Server]]
