Bug reporting for KDE 4

[Alexander Neundorf]

On Sunday 28 October 2007, Andreas Hartmetz wrote:
> Hi all,
>
> I've just had this idea ("Oh noes!" I hear you scream)...
> We have *lots* of bugs in KDE 4 and we all hit them all the time, right?
> There is also quite some confusion about where/if/how to report them
> Bugzilla? Heavyweight, slow, I fscking hate bugzilla (MHO) and avoid it.
> Mailing lists? Pushes down SNR on development lists.
> A wiki? Not really suited to very unstructured information and
> conversation-style exchange. It can be done but (again IMHO) it doesn't
> feel right.
>
> What about a special mailing list just for bugs in KDE 4, large and small?
> kde4-bugs, kde4-crunch, whatever. The biggest advantage over the regular
> mailing lists would be that it's explicitly encouraged to report
> *everything*, however small. Additionally, people generally don't watch or
> participate in all mailing list and one usually tests more things than the
> ones covered by one's list memberships.

...
To me this email reads: "bug trackers suck !" or "the KDE bug tracker is not 
good enough for all our needs"

While your mail sounds good, I have the feeling using a mailing list for bug 
reporting is a step backwards. I agree that reporting bugs for a project in a 
quite buggy state in the official bug tracker also feels wrong.

Bug trackers have advantages over emails, like you can't delete bugs, you can 
mark them as closed, you also get emails on changes etc.
Reporting a bug in bugzilla is quite some work, also searching in bugzilla.

How about setting up (I guess we don't have man power/machines/time etc. to do 
it) a dedicated bug tracker for current (I know this is more than 
stretchable) bugs ?
E.g. mantis (easy to setup AFAIK) with accounts for everybody with svn 
access ?

Alex