Report a Bug
The best way to report a bug is with the bug
report tool on the MrBayes Sourceforge project page. With this tool one can look at previously reported bugs. Choose the any
option at the status drop down box to browse bugreports that where solved (closed). If the problem you have encountered is not listed here, you can submit a
new bugreport by clicking the Submit New link. Sourceforge uses the
term tracker item for a bug report.
Submit a new bug

A screen shot of the bug report tool.
On the bug report page there are a few optional choices:
- Category: Where did the bug appear, e.g. in the MPI part.
- Group: In which version of MrBayes did the bug appear, e.g. version 3.1 or version 4.
In the mandatory fields Summary and Detailed Description you can describe the bug. Keep in mind that the best
way for us to solve the bug is if we can repeat it. See for example, the article
How to Report Bugs Effectively.

Attach files to your report.
The bug tool allows you to attach files to your bug report. These can be datasets with which you had the problem or the
console output of the MrBayes program. You can find this upload option at the end of the report page.
When you are satisfied with your report, you can submit it by
pressing the submit button. Although Sourceforge asks you
to login, you don't have to. The bug report will then be filled
anonymously, but you might want to at your email address in
the report so we can contact you about the bug report.
Mailing list
A great aid for resolving problems with MrBayes is the MrBayes mailing list.
If you have a general question about MrBayes you can ask it by posting the question to the mailing list. To post on this list you
have to be subscribed to it. The list archive
is accessible for everyone.
|