SharpDevelop Community

Get your problems solved!
Welcome to SharpDevelop Community Sign in | Join | Help
in Search

Making useful bug reports

Last post 09-22-2005 2:27 PM by BernhardSpuida. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 09-22-2005 2:27 PM

    Making useful bug reports

    Locked Reply Contact
    We are receiving a lot of bugreports here in this forum, but most of them are very poor and make it very, very hard for us to reproduce the bug and find a fix. This is the reason for this little guidance - after all, you have a problem and we want to help you, so please make helping you as easy as possible.

    How to make good bug reports

    1. Use this forum to report bugs, place known bugs also in the wiki
    2. Describe what you wanted to do and how you did it
    3. Describe the expected result
    4. Describe the actual result
    5. Attach the exception text and the stack trace

    A good bug report complies with at least 4 items from the list. If your bug report complies with 3 or less items, it is poor and this means it will take much more time to fix (when it's not ignored).

    To avoid duplicate bug reports, please read the 'General Users FAQ' forum.
    These will perhaps also give workarounds for the problems you are experiencing.

    If you are reporting bugs found in repository code, not the official releases, we
    offer a mailing list for the users of our Subversion repository:

    There you can report problems you encounter with the repository builds and discuss the builds. Please also state whether you are reporting a bug in a Fidalgo or a Corsavy repository build.

    Specifically for the discussion of Corsavy - not only bug reports, but also discussion of features etc. we now have a forum.
Page 1 of 1 (1 items)
Powered by Community Server (Commercial Edition), by Telligent Systems
Don't contact us via this ( email address.