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 290228
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: One word
by eMPee584 on Wed 12th Dec 2007 14:18 UTC in reply to "RE[3]: One word"
Member since:

dear superstoning one,
please make them give the closed bugs a differentialable tag so you can actually see what the reason for closing the bug was. Else the result will be like throwing two haystacks together: a grey, gooey pile...
Why so? --- I definitly want to have a go at the KDE code base soon (=when I got some more time) and even want to fix my own bugs, and BACKPORT them. BACKPORTING is a goood thing to do, you know?

Edited 2007-12-12 14:19

Reply Parent Score: 1

RE[5]: One word
by superstoned on Wed 12th Dec 2007 14:36 in reply to "RE[4]: One word"
superstoned Member since:

I don't stone anyone ;-)


anyway, yeah, we should give these automatically closed bugs a special tag (I guess that's what you want, right).

We also plan to send an email to the reporter, telling them their bug will be closed in 2 months unless they check if the bug is actually stil valid (including some hints on how to check).

If you want to backport fixes, no problem, 3.5.9 is sure open for that, and we do backport fixes ourselves and will continue to do that for a while. Of course, we don't want to spend TOO much time on it, as we also want to ensure KDE 4 is good ;)

Reply Parent Score: 2