summaryrefslogtreecommitdiffstats
path: root/doc/src/bughowto.qdoc
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@nokia.com>2009-11-11 16:37:48 (GMT)
committerVolker Hilsheimer <volker.hilsheimer@nokia.com>2009-11-11 16:45:15 (GMT)
commitde76200652e05de34d99f111c64a051a49911034 (patch)
tree904d7565180809b668a7a14537657f6ebb7ad94c /doc/src/bughowto.qdoc
parentd1d6769da76a9ff83fd56e12bd331c5e4858ccca (diff)
downloadQt-de76200652e05de34d99f111c64a051a49911034.zip
Qt-de76200652e05de34d99f111c64a051a49911034.tar.gz
Qt-de76200652e05de34d99f111c64a051a49911034.tar.bz2
Doc: Link to the public bug tracker.
Diffstat (limited to 'doc/src/bughowto.qdoc')
-rw-r--r--doc/src/bughowto.qdoc26
1 files changed, 17 insertions, 9 deletions
diff --git a/doc/src/bughowto.qdoc b/doc/src/bughowto.qdoc
index 971634a..e9ae965 100644
--- a/doc/src/bughowto.qdoc
+++ b/doc/src/bughowto.qdoc
@@ -48,24 +48,32 @@
about it so that we can fix it.
Before reporting a bug, please check the \l{FAQs}, \l{Platform
- Notes}, and the \l{Task Tracker} on the Qt website to see
+ Notes}, and the \l{Qt Bug Tracker} on the Qt website to see
if the issue is already known.
- If you have found a new bug, please submit a bug report using
- the \l{Bug Report Form}. Always include the following information
- in your bug report:
+ The first thing you should do is to sign up for an account for
+ the \l{Qt Bug Tracker}, if you do not already have one. Once you
+ have done that you can submit and track your bug reports and they
+ will be publicly available from the moment you submit them.
+
+ Always include the following information in your bug report:
\list 1
\o The name and version number of your compiler
\o The name and version number of your operating system
\o The version of Qt you are using, and what configure options it was
- compiled with.
+ compiled with
+ \o Reliable and clear description on how to reproduce the problem
\endlist
+
+ If possible, please provide a test written using the QtTest module
+ as this will improve the procedure of reproducing your problem and
+ allow the developers to address the issue in a more efficient way.
- If the problem you are reporting is only visible at run-time, try to
- create a small test program that shows the problem when run. Often,
- such a program can be created with some minor changes to one
- of the many example programs in Qt's \c examples directory.
+ Otherwise, if the problem you are reporting is only visible at run-time,
+ try to create a small test program that shows the problem when run.
+ Often, such a program can be created with some minor changes to one of
+ the many example programs in Qt's examples directory.
If you have implemented a bug fix and want to contribute your fix
directly, then you can do so through the \l{Public Qt Repository}.