rev 3756 - trunk/packages/kdebase/debian

[Pierre Habouzit]

Author: madcoder
Date: 2006-05-14 21:13:30 +0000 (Sun, 14 May 2006)
New Revision: 3756

Added:
   trunk/packages/kdebase/debian/konqueror.presubj
Modified:
   trunk/packages/kdebase/debian/changelog
Log:
add a presubg for konqueror: it is responsible of 161 bugs on the 510
attributed to kdebase (!?!?)

will do the same in kdenetwork (presumably for kopete) and kdepim
(presumably for kmail and kontact ?)



Modified: trunk/packages/kdebase/debian/changelog
===================================================================
--- trunk/packages/kdebase/debian/changelog	2006-05-14 20:39:45 UTC (rev 3755)
+++ trunk/packages/kdebase/debian/changelog	2006-05-14 21:13:30 UTC (rev 3756)
@@ -31,6 +31,10 @@
   * Add 'ru' debconf templates translation, thanks to Yuriy Talakan.
     (Closes: #367206)
 
+  * add konqueror.presubj (konqueror is responsible of 25% of the kdebase bug
+    reports) to ask for more precise bug reports, because missing the
+    primordial informations to make them of any use.
+
  -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Sun, 14 May 2006 08:49:25 -0400
 
 kdebase (4:3.5.2-2) unstable; urgency=low

Added: trunk/packages/kdebase/debian/konqueror.presubj
===================================================================
--- trunk/packages/kdebase/debian/konqueror.presubj	2006-05-14 20:39:45 UTC (rev 3755)
+++ trunk/packages/kdebase/debian/konqueror.presubj	2006-05-14 21:13:30 UTC (rev 3756)
@@ -0,0 +1,29 @@
+Reporting a konqueror crash
+---------------------------
+
+It is important when you report a konqueror crash to provide:
+ * the exact steps to reproduce the crash (URL of the site, the exact
+   actions you performed, ...)
+ * a useful backtrace of the crash.
+
+To produce useful backtrace you must have kdelibs-dbg and kdebase-dbg
+installed. A backtrace full of "(no debugging symbols found)" is useless.
+
+A bug that is not reproducible, or that lack the necessary backtrace, will
+be discarded.
+
+
+Reporting a rendering bug
+-------------------------
+
+Please provide the URL of the page that don't display correctly. explain
+clearly what you expect, and what you get.
+
+Small screenshots of the part that has a problem are of great help and can
+be attached to the bug report. Screenshots of the "correct" behaviour
+(taken on another graphical browser) may also help.
+
+Any bug that states "Site foo is not rendered correctly" with no more
+explanation will be discarded (even if at the report time the defect is
+obvious: it is too difficult to check if the defect is still there)
+