Bug Triaging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
'''''This page is outdated. Please see: "Guidelines for Triaging bugs":http://wiki.qt.io/Triaging_Bugs instead.''''' | '''''This page is outdated. Please see: "Guidelines for Triaging bugs":http://wiki.qt.io/Triaging_Bugs instead.''''' | ||
Revision as of 15:08, 3 March 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
This page is outdated. Please see: "Guidelines for Triaging bugs":http://wiki.qt.io/Triaging_Bugs instead.
Bug Triaging (old version)
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.)