Trace: » roadmap » guide » metric » soc_dicing_optimisation » todo » bug_reporting
Submitting a Bug Report
When reporting what you believe to be a bug, please take the time to provide as much information as possible. The more detailed your report, the more likely the developers are to find the problem and provide a fix. Please consider the following points when preparing your bug report.
- Provide exact information about which version of Aqsis you are using, available by typing
aqsis –versionon the command line. - Provide exact information about which OS you are using, including which version, which distro (where appropriate) and any relevant information regarding service packs.
- Let us know how you installed Aqsis.
- Did you build it, if so, what tools and which version did you use?
- Did you install it from a binary installation, if so, where did you get it?
- Provide as much information as possible regarding the nature of the fault.
- Where did the content come from?
- What command line options did you supply to Aqsis?
- Do you have a custom
aqsisrc, if so please attach that to the bug report.
- Please provide sample data that allows us to reproduce the bug.
- Please ensure that the data is as simple as possible while still reproducing the bug. Providing a multi-megabyte RIB file in which only a single primitive actually causes the problem will reduce the likelihood of a developer addressing the problem. Any assistance you can give to the process of identifying the exact cause of the problem will improve the chances of a quick solution.
- Check the existing bug report list at SourceForge's Bug Tracking System to see if there is already a report that matches your problem.
Prioritisation
When prioritising a bug report, use the following chart as a guide. Note that this doesn't represent a hard and fast rule, just a guideline, there will be cases not covered by this chart. If you have any problems identifying the appropriate priority for a bug, ask on one of the various support forums.
