Bug Triaging: Difference between revisions
Jump to navigation
Jump to search
AutoSpider (talk | contribs) (Convert ExpressionEngine links) |
(Mark as Outdated, remove Cleanup tag) |
||
Line 1: | Line 1: | ||
{{ | {{Outdated | reason=See [[Triaging Bugs]] instead. |}} | ||
When evaluating an incoming bug, please follow these steps: | When evaluating an incoming bug, please follow these steps: |
Revision as of 12:35, 19 March 2015
IMPORTANT: The content of this page is outdated. Reason: See Triaging Bugs instead. If you have checked or updated this page and found the content to be suitable, please remove this notice. |
When evaluating an incoming bug, please follow these steps:
- Try to reproduce the issue, especially if it was reported against an earlier version than the latest Qt version (it might already be fixed)
- If you manage to reproduce the bug, try to come up with an easy way of reproducing it. Perhaps you can use one of the manual tests (we have a ton of manual tests in qtbase and many compile against 4.8 as well)
- If it is a crash, try to add a stacktrace
- If the user provided sample code snippets, try to create a small example that ideally runs Qt 4.8/5, and prints the QT_VERSION_STR somewhere to avoid pilot errors (Creator 2.7 has a nice "Create project from Code snippet" wizard - see Other Projects/Code Snippet)
- If you know how to fix it, feel free to provide a patch :)
- If not: Add a priority and assign it to the right person, if you know who that is. (If not, you can also leave it unassigned.)