|
|
181.
|
|
|
<emphasis>Congratulations on making a successful non-crash related bug report!</emphasis> Identifying and reporting bugs are essential to improving <trademark>Kubuntu</trademark>. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:1048(para)
|
|
|
182.
|
|
|
Filing a Feature Request or Wishlist Report
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:1058(title)
|
|
|
183.
|
|
|
The easiest way to request a new feature, in either an application or the operating system, is to file a bug — otherwise known as a wishlist report.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:1059(para)
|
|
|
184.
|
|
|
Filing a feature request report in <trademark>KDE</trademark> is exactly the same as filing a <link linkend="filing-non-crash-kde">non-crash <trademark>KDE</trademark> bug report</link>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:1067(para)
|
|
|
185.
|
|
|
Filing a wishlist report for <trademark>Kubuntu</trademark> is exactly the same as filing a <link linkend="filing-non-crash-lp">non-crash <trademark>Launchpad</trademark> bug report</link>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:1075(para)
|
