12 | | Bug report submissions should be submitted to the [http://webkit.org/new-bug webkit bugzilla] using the 'WebKit Qt' product according to the standard [http://webkit.org/quality/reporting.html reporting guidelines]. |
| 12 | Bug reports, feature requests, and patches for the Qt-port of WebKit should all be submitted to the [https://bugs.webkit.org/enter_bug.cgi?product=WebKit&version=525%2B%20%28Nightly%20build%29&component=New%20Bugs&bug_severity=Normal&keywords=Qt&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=&commentprivacy=0&dependson=&blocked=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug&priority=P3 WebKit Bugzilla]. |
| 13 | |
| 14 | Please follow the standard [http://webkit.org/quality/reporting.html reporting guidelines] and [http://webkit.org/quality/bugwriting.html steps for writing good bug reports], |
| 15 | with the following spesifics for the Qt port: |
| 16 | |
| 17 | * '''All bugs related to the Qt port of WebKit should have the keyword 'Qt'''' |
| 18 | |
| 19 | * Use the component to specify which area of the code you're targeting |
| 20 | * There are components for rendering, plugins, tests, text, forms, etc. |
| 21 | * The 'WebKit Qt' component should only be used for bugs/features in the QtWebKit API |
| 22 | |
| 23 | * Add the keyword 'Performance' if the bug is performance-related |
| 24 | |
| 25 | * Use the severity 'Enhancement' for feature-requests/enhancements |
| 26 | * Use the severity 'Blocker' for compilation errors/build breaks |
| 27 | * Use the severity 'Critical' for crashes |
| 28 | * Use the severities 'Minor, Normal, Major' for bugs |