Skip to topic | Skip to bottom

You are here: FAQs > SupportFAQ > BugReportGuidelines
FAQs.BugReportGuidelines r1.1 - 24 Apr 2008 - 19:03 - AndrewBenson topic end


Start of topic | Skip to actions

Bug Reporting Guidelines

BUG REPORTING GUIDELINES

Please report any problems you experience with clear and complete information, including steps to reproduce, software and system information, and where possible, an isolated example patch and crash log. Something like the following would be ideal. This makes it easier for us to find and fix the problems you experience. Without such clear and complete information, it is less likely we will be able to.

Summary: Provide a descriptive summary of the issue.

Steps to Reproduce: In numbered format, detail the exact steps taken to produce the bug.

Expected Results: Describe what you expected to happen when you executed the steps above.

Actual Results: Please explain what actually occurred when steps above are executed.

Regression: Describe circumstances where the problem occurs or does not occur, such as software versions and/or hardware configurations.

Notes: Provide additional information, such as references to related problems, workarounds and relevant attachments.
to top


You are here: FAQs > SupportFAQ > BugReportGuidelines

to top

Copyright © 2007 Cycling '74. All Rights Reserved.

...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT...WEBCOPYRIGHT... porn free porn