Changes between Version 61 and Version 62 of QtWebKitContrib


Ignore:
Timestamp:
Mar 2, 2010 8:09:10 AM (11 years ago)
Author:
vestbo@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitContrib

    v61 v62  
    55== Reporting Bugs ==
    66
    7 Bug reports, feature requests, and patches for the Qt-port of WebKit should all be submitted to the WebKit Bugzilla.
     7Bug reports, feature requests, and patches for the Qt-port of WebKit should all be submitted to the [http://webkit.org/new-qtwebkit-bug WebKit Bugzilla].
    88
    9 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],
    10 with the following specifics for the Qt port:
     9Please follow the standard WebKit [http://webkit.org/quality/reporting.html bug reporting guidelines] and [http://webkit.org/quality/bugwriting.html steps for writing good bug reports], but take note of the following QtWebKit specifics.
     10
     11=== Component ===
     12
     13The [https://bugs.webkit.org/describecomponents.cgi?product=WebKit component] is used to signify the rough are that the bug relates to. If you don't know which one to choose leave the component at 'New Bug'. It's better to leave it at 'New Bug' than to choose one at random.
     14
     15'''Note:''' the 'QtWebKit' component should be used for bugs/features in the QtWebKit ''API'' layer, '''not''' to signify that the bug is a Qt-bug in general (see below).
     16
     17=== Version ===
     18
     19Leave at 'nightly build'. You should always test a bug against a nightly build of QtWebKit to make sure that it's still valid before reporting.
     20
     21=== Severity ===
     22
     23The [https://bugs.webkit.org/page.cgi?id=fields.html#bug_severity severity] is a signifier of what ''kind'' of bug we're talking about/how serious it is, and should not be confused with [https://bugs.webkit.org/page.cgi?id=fields.html priority], ie, when it will/should be be fixed (see below).
     24
     25Use the following rules of thumb when deciding on a severity:
     26
     27 * Use 'Blocker' for compilation errors/build breaks
     28 * Use 'Critical' for crashes, loss of data, severe memory leak
     29 * Use 'Enhancement' for feature-requests/enhancements
     30
     31The severities 'Minor, Normal, Major' should then be used for "normal" bugs which don't fall into either of these categories, ranging from minor loss of function, or other problem where easy workaround is present, to major loss of function.
     32
     33=== Platform and OS ===
     34
     35Choose the settings most relevant to where you found the bug, or 'All' if you've confirmed that the bug exists on more than one platform.
     36
     37'''Note''': These two fields should not be used to signal which ''port'' of WebKit we're dealing with, but the underlying platform and OS.
     38
     39=== Priority ===
     40
     41This field is set by developers when scheduling and triaging tasks, please leave this at the default priority.
     42
     43=== Keywords ===
     44
     45We need a way to track bugs that are specific for the Qt port of WebKit. The right way to do this is using the 'Qt' [https://bugs.webkit.org/describekeywords.cgi keyword] (you may not see the keywords entry field until after creating the bug. If so, please add the keyword after creating the bug).
    1146
    1247 * '''All bugs related to the Qt port of WebKit should have the keyword 'Qt''''
    13 
    14  * Use the component to specify which area of the code you're targeting
    15    * There are components for rendering, plugins, tests, text, forms, etc.
    16    * The 'WebKit Qt' component should only be used for bugs/features in the QtWebKit API
    17 
    1848 * Add the keyword 'Performance' if the bug is performance-related
    1949
    20  * Use the severity 'Enhancement' for feature-requests/enhancements
    21  * Use the severity 'Blocker' for compilation errors/build breaks
    22  * Use the severity 'Critical' for crashes
    23  * Use the severities 'Minor, Normal, Major' for bugs
     50'''Note:''' Do not use the 'QtWebKit' ''component'' to signal that it's a Qt bug. The QtWebKit component is used for bugs/features in the QtWebKit ''API'' layer, '''not''' to signify that the bug is a Qt-bug in general.
    2451
    25 You can use [http://webkit.org/new-qtwebkit-bug http://webkit.org/new-qtwebkit-bug] as a handy template.
    26 
    27 === Useful filters for existing Qt bugs ===
     52== Useful filters for existing Qt bugs ==
    2853[https://bugs.webkit.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=WebKit&long_desc_type=allwordssubstr&long_desc=&bug_status=UNCONFIRMED&bug_status=NEW&keywords_type=allwords&keywords=Qt&order=Importance Bugs (unconfirmed or new)]
    2954[https://bugs.webkit.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=WebKit&component=Accessibility&component=CSS&component=Evangelism&component=Forms&component=Frames&component=History&component=HTML+DOM&component=HTML+Editing&component=Images&component=Java&component=JavaScriptCore&component=JavaScriptGlue&component=Layout+and+Rendering&component=Page+Loading&component=PDF&component=Platform&component=Plug-ins&component=Printing&component=SVG&component=Tables&component=Text&component=Tools+%2F+Tests&component=Web+Inspector&component=Web+Template+Framework&component=WebCore+JavaScript&component=WebCore+Misc.&component=WebKit+API&component=WebKit+Gtk&component=WebKit+Misc.&component=WebKit+Qt&component=WebKit+Website&component=WebKit+wx&component=XML&component=XML+DOM&long_desc_type=allwordssubstr&long_desc=&bug_status=ASSIGNED&bug_status=REOPENED&keywords_type=allwords&keywords=Qt&order=Importance Bugs (assigned)]