Bug Reporting and Tracking

To report bug or other issues, create a new issue on Google Code. Also, feel free to join the tinymux list and report bugs there, or E-mail bug reports to the E-mail address indicated in your readme files.

The devteam has worked very hard to ferret out and fix as many of the crashing/corrupting bugs in the server as possible. For the cases where you do find bugs, we would like you to take the time to give us as much data as possible about the bug.

Each bug report we receive will be assigned a number from 1 to 4 according to severity (how much pain it causes) and prioritized from 1 to 3 according to how beneficial it would be to fix it relative to other bugs on the list.

Please double check to be sure it really is a bug and not a new feature or design decision. This is important to the process, as it may mean that something was missed in the documentation and needs to be made clearer. The simple test is that if the server crashes, it's a bug and if you can't tell, report it as one.

Try to reproduce and document the sequence of events that will demonstrate the bug. This will help the dev team identify the problem sooner. The 'log' configuration parameter may be very helpful in this process.