Changes between Version 18 and Version 19 of QtWebKitBugs


Ignore:
Timestamp:
Mar 16, 2010 4:36:40 AM (10 years ago)
Author:
jocelyn.turcotte@nokia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitBugs

    v18 v19  
    4545[http://en.wikipedia.org/wiki/Triage Triaging] bugs basically means sorting out the good bug reports from the bad ones. It's an important step for keeping the bug database clean and maintainable.
    4646
    47 The following steps are used by the developers when triaging QtWebKit bugs:
     47The following steps are used by the developers when triaging !QtWebKit bugs:
    4848
    4949  1. Verify that the bug report has a test-case
     
    5757     * P1 means the bug should ideally be fixed for the next release (typically crashes or other serious bugs)
    5858     * P2 means the bug is important, but not critical for a release like P1s are
    59      * P3 means the bug is valid, but due to limited resources in the QtWebKit team it is considered after P1s and P2s. If a P3 bug is important to you, see the QtWebKit [https://trac.webkit.org/wiki/QtWebKitContrib contribution guidelines] on how to help getting it fixed.
     59     * P3 means the bug is valid, but due to limited resources in the !QtWebKit team it is considered after P1s and P2s. If a P3 bug is important to you, see the !QtWebKit [https://trac.webkit.org/wiki/QtWebKitContrib contribution guidelines] on how to help getting it fixed.
    6060  1. If the status is UNCONFIRMED, set it to NEW.
    6161  1. Change the assignee from webkit-unassigned@webkit.org to webkit-qt-unassigned@trolltech.com. This marks the bug as triaged, and will notify people who are watching the list of triaged bugs.
     
    6868If 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.
    6969
    70 '''Note:''' the 'QtWebKit' component should only be used for bugs/features in the public QtWebKit ''API'' layer, '''not''' to signify that the bug is specific to the Qt port of WebKit (see Keywords]).
     70'''Note:''' the '!QtWebKit' component should only be used for bugs/features in the public !QtWebKit ''API'' layer, '''not''' to signify that the bug is specific to the Qt port of WebKit (see Keywords]).
    7171
    7272=== Severity ===
     
    9696 * Add the keyword 'Performance' if the bug is performance-related
    9797
    98 '''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.
     98'''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.
    9999
    100100=== Version ===
    101 Leave 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.
     101Leave 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.
    102102
    103103=== Priority ===