Changes between Version 18 and Version 19 of QtWebKitBugs

Timestamp:

Mar 16, 2010, 4:36:40 AM (15 years ago)

Author:

jocelyn.turcotte@nokia.com

Comment:

--

QtWebKitBugs

@@ -45 +45 @@
 [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.
 
-The following steps are used by the developers when triaging QtWebKit bugs:
+The following steps are used by the developers when triaging !QtWebKit bugs:
 
   1. Verify that the bug report has a test-case
@@ -57 +57 @@
      * P1 means the bug should ideally be fixed for the next release (typically crashes or other serious bugs)
      * P2 means the bug is important, but not critical for a release like P1s are
-     * 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.
+     * 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.
   1. If the status is UNCONFIRMED, set it to NEW.
   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.
@@ -68 +68 @@
 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.
 
-'''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]).
+'''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]).
 
 === Severity ===
@@ -96 +96 @@
  * Add the keyword 'Performance' if the bug is performance-related
 
-'''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.
+'''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.
 
 === Version ===
-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.
+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.
 
 === Priority ===