Linked by Thom Holwerda on Tue 11th Dec 2007 20:50 UTC, submitted by diegocg
KDE Some interesting tidbits concerning KDE 4. Firstly, there is a debate whether to close all bugs of KDE 3.x (or not) once 4.0 has been released; you can vote on a poll posing this question too. Secondly, some unscientific benchmarks show that KDE 4.0 from svn is less resource hungry than current KDE 3.x builds. Update: KDE 4.0 RC2 has been released.
Thread beginning with comment 290414
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Control
by Havin_it on Thu 13th Dec 2007 12:02 UTC in reply to "Control"
Havin_it
Member since:
2006-03-10

I think it cuts both ways. I have in the past filed/contributed to a couple of bugs on bugs.kde.org and I'd have to say I was left with little desire to go back.

For the record, I named the affected component (and version) and summarised the problem in the title in both cases, and gave details of the OS/version and compiler settings, related configs and reproduction steps in the body. On request, I produced relevant log-output for one of the bugs.

Now were either of these bugs a duplicate? It'd be hard to say for sure, though I did my best to search for any possible dupes. Why am I not sure? Because bugs.kde's search is very dumb and searching successfully is (in my experience) a real trial. This is true of most bug-dbs to be honest, but KDE's is the most rudimentary I've seen.

What really broke my spirit though was the lack of response. Again KDE are not alone in this, but the silence can be deafening. At least in one instance I was asked for some further data, but there hasn't been any reply since I submitted that (about 18 months ago), even to say "well, that didn't help unfortunately."

I believe I've been attempting to help both KDE and myself by reporting bugs, but where is the motivation to keep doing so when you doubt whether anyone is listening?

Reply Parent Bookmark Score: 1