Yet another failed KDE release?

dE . de.techno at
Thu Mar 28 05:15:25 GMT 2013

On Sat, Mar 23, 2013 at 10:42 PM, Anne Wilson
<cannewilson at> wrote:
> Hash: SHA1
> On 23/03/13 13:08, dE . wrote:
>> There's very less time focused on testing; that should be
>> increased, and there's really no reason to hurry releases, no one
>> complained KDE is empty and featureless, but a lot complain about
>> it's bugs and stability. This should point to something.
>> Sorry:This discussion is getting a bit heavy, I'll take some time
>> to respond.
> No distro forces you to use the latest of everything.  Usually any
> version is supported for at least a few months after the release of a
> new one, so you can always stick with that.
> You claim to be happy to help test, yet you complain constantly.
> Let's try for some facts.

I'm complaining right now, cause I see all this in the stable release (4.10.1).

This makes early testing the releases more important, cause it
reflects the state of KDE.

> Have you any idea how many different graphics cards are in use by the
> KDE community - i.e. by all users?  Sound cards?  and that's just the
> obvious ones.  How is any developer going to test every one of those?
>  It's simply not possible.  Early adopters choose to be guinea pigs,
> helping testing.  If you or anyone else doesn't want to be in that
> situation, simply stick with the older version.

Thats's exactly why there should be more time to test RCs and the RC
releases should be slow.

Not everyone runs the same distro, or hardware, so KDE should be
tested for maximum backends and libraries, which may revile new bugs;
which as of the current time hits end users, and after that bugs are
reported, which often lasts for years, cause devs are busy preparing
for the next release.
This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list