MantisEtiquette
De DigiWiki.
When filing a Mantis issues, there are a few simple things that must be followed for your bug to be reviewed. These guidelines are explained in this document and will help you successfully file a good bug report. When to report a Mantis issue
You should report a Mantis issue when an issue that you are having in your sim repeatedly is occurring. You should also report an issue if something crashes or hinders your ability to use Aurora-Sim. Before you submit a Mantis issue, please check the Mantis tracker to see whether the bug you are seeing has already been reported, and if so, do not open another issue on it, reuse the same issue that was already reported. You should not report Mantis issues that have not been checked and are invalid. The Naming of a Mantis issue
When filing a bug report, it needs to have an appropriate name. It should have a very simple way of explaining what the bug/feature request is, and what is wrong. Please use correct spelling (as close as possible anyway) and correct capitalization on the name and description of the issue. Furthermore, if the report you are filing is about a feature request, please put this in front of the name of the Mantis report, "[Feature]: " (without the quotes). Other Mantis information
When filing a Mantis report, please give the information about what operating system you are on, as well as the version of Aurora that you are currently using. If you are using a release, please give the release you are on, otherwise, give the rit revision you are using. If you are having an issue with the database, please give what database you are using (MySQL, SQLite, FileBased) and the version of it (MySQL only). Give the configuration in which you are using and experiencing the bug in (standalone, Aurora.Server, region attached to Aurora.Server, region attached to Robust). Mantis Issue Feedback
When a Mantis issue has been reviewed by a developer, and the developer has requested some information, the issue will be set to "Feedback". This is not to be set by users, only developers. Once an issue has been set to "Feedback", feedback on the issue is expected within a week, perhaps more depending on the issue. If feedback is not given, and other users comment on the issue and it appears to be fixed, the issue will be closed. Patches
Patches are very welcome in the Mantis tracker! If you have a patch, set the issue to "Patch Exists" so that other developers will notice it, and if possible change the name so that it starts with "[Patch]: ". When to Resolve an issue
When you (the reporter) believe an issue is fixed, you may "Resolve" the issue and (if necessary), add some info for other users that may be seeing the bug. Do not "Close" the issue, just "Resolve" the issue, the "Closed" will be done later by a developer. Commenting on Mantis issues
You may comment on any Mantis issues available to you, as long as the comments are constructive and helpful to all. If your comments are not helpful, and cause problems for other users, you may after repeated warnings, lose your ability to comment on certain Mantis issues.
