Bug reporting for KDE 4

[Andras Mantia]

I agree with most of what you've listed about bugzilla's problems. Still,
bugs.kde.org is the way to go, because with a mailing list things will be
forgotten and hard to track. What happens if somebody reports the bug, it
doesn't get fixed before 4.0 final? The bug will be forgotten, unless
somebody reports again through bugzilla.
And why is it different a mailing list than getting mails from
bugs.kde.org for bugs that affect your product? You can even reply through
mail.
 With bugzilla you are in personal contact with your users, with a mailing
list used to report random bugs for different products, this contact is
not so close.
 If there are more developers for a product, a separate mailing list can
be used for them where all of them can read the bugs/comment on them.
 What should be done is to have a clear way to identify development
version reports, instead of those svn, svn-trunk, etc. strings. Actually
as I see this is done in the reporting wizard, the problem is in the
querying part. Maybe there database needs to be cleaned up, so those
strings are unified to one.
And if you want to help the users to report the problems easier, the none
wizard interface could be enabled during the RC period, for example.

Andras