From kde-devel Tue Aug 29 09:17:38 2006 From: Philip Rodrigues Date: Tue, 29 Aug 2006 09:17:38 +0000 To: kde-devel Subject: Re: konqueror has 1305 unconfirmed bugs Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=115684310121624 Lex Hider wrote: > Holy crap! > You don't know how exciting this is for me. I have had a few previous > attempts in private at tackling this problem and get burnt out after a > while. Check out: Hopefully we canget round this with more people - many hands make light work, and all that :-). > * I'm totally against autoclosing old bugs. One of the strategies I have > adopted for old bugs that I couldn't reproduce/understand or that were > obscure was to make a comment like "is this still an issue for you > ". Often you would get a response like, yeah it's fine > now in kde X.X. Or, still get it in latest kde. Then I would close if > there was no response in a few weeks. Agreed - the KMail folks have this specifically written down as a policy: http://wiki.kde.org/tiki-index.php?page=Kmail%20Bug%20Management I've asked the konq developers whether they have anything similar, so we can follow exactly what they are doing. > * check out: > > http://bugs.kde.org/show_bug.cgi?id=84953#c4 Well, he got what he paid for... > Our bugzilla is one of the most important interfaces between kde > developers and users. Bugrot is one of the biggest problems I can see > that kde has. There are scores of old kde bugs that have had no response > to them. This means that as far as the user is aware, no one has seen > their report, or that they don't care about it. I think we need some > kind of target for responses to bug reports. This is a fair point though. > I think a target for unconfirmed konqueror bugs would also be a nice > idea. Provided there is the resources to achieve it, this could be a good plan. Maybe it's worth investigating setting up a KDE bugs team, like the GNOME one: http://live.gnome.org/Bugsquad > * check out: > > http://lists.kde.org/?l=kfm-devel&m=114586667407423&w=2 > > Can bughunter's please mark site specific bugs like this. > Marking the summary [site-issue] doesn't necessarily mean that it is the > site's bug and not konqueror. It is just a helpful way to categorize > more general konqueror bugs from site specific ones. Ack, thanks for the reminder. Regards, Philip -- KDE Documentation Team: http://i18n.kde.org/doc KDE Documentation Online: http://docs.kde.org >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<