|
|
58.
|
|
|
Generally, there are three types of bug reports: <emphasis>crash</emphasis>, <emphasis>non-crash</emphasis>, and <emphasis>feature request</emphasis>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:24(para)
|
|
|
59.
|
|
|
Overview of bug types
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:29(title)
|
|
|
61.
|
|
|
An application or system crash or failure. Most of the time a crash dialog will be presented. This can be turned into a bug report.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:35(para)
|
|
|
63.
|
|
|
A bug or regression that doesn't cause the application to crash, but does cause the application to stop functioning properly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:46(para)
|
|
|
64.
|
|
|
Feature request
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:53(term)
|
|
|
65.
|
|
|
Also known as a wish list item, this type of report is filed to add a function to an application, or to change something in the application that isn't due to a regression or a crash.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:57(para)
|
|
|
66.
|
|
|
Bug Trackers Used By <trademark>Kubuntu</trademark>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:68(title)
|
|
|
67.
|
|
|
KDE's Bugtracking System
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:71(title)
|
|
|
68.
|
|
|
<trademark>KDE</trademark> uses <trademark>Bugzilla</trademark>, a <quote>Defect Tracking System</quote>. <trademark>Bugzilla</trademark> is one of the most popular tools used in the open source development community.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:75(para)
|
|
|
69.
|
|
|
Register first
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:81(title) docs/bugs/C/bugs.xml:110(title) docs/bugs/C/bugs.xml:672(title)
|
