Reporting bugs: Difference between revisions
Dan Polansky (talk | contribs) (+See also) |
Dan Polansky (talk | contribs) (-signature; these are for talk pages) |
||
| Line 19: | Line 19: | ||
* Clear instructions on how to reproduce the failure | * Clear instructions on how to reproduce the failure | ||
* Sometimes it helps if you send us the actual mindmap where the problem occurred. | * Sometimes it helps if you send us the actual mindmap where the problem occurred. | ||
==See also== | ==See also== | ||
Revision as of 12:30, 11 May 2009
Reporting bugs
The most important thing you can do to help us find and fix the bugs you report, is to make sure that you give us enough information that we can reproduce the bug. Otherwise, we have no way of knowing, for sure, that we've fixed the bug you report.
The first thing you should do, when reporting a bug, is double-check your setup, especially if you are just getting started. Make sure you are using the correct version of the Java Runtime Environment. (Currently, FreeMind is compiled and run under Java 1.4. Some of us run it under Java 1.5, and FreeMind 0.9.0 should work with 1.6 too) Make sure you have your Path and ClassPath variables set correctly.
Place
Please report the bugs to SourceForge's Bug Tracker. Still, getting your bug report at least in forum is better than not getting it at all.
Information to be provided
Here are some things that help:
- The version of FreeMind you are using.
- What operating system you are running.
- The version and patch level of your OS. (For example XP Professional Service Pack 2)
- What you were trying to do when you got the failure
- A description of the failure
- Clear instructions on how to reproduce the failure
- Sometimes it helps if you send us the actual mindmap where the problem occurred.
