A few words about the Quality of KDE 4.2

[Samuel Kage]

Am Sonntag 22 März 2009 16:29:13 schrieb Kevin Krammer:
> How does one determine that it is an obvious bug and not something related
> to the current setup, e.g. new user account or upgrade from a specific
> version or packages from a specific vendor?
>
> I have been doing user support for quite some time now and there have been
> times when one could perfectly determine the user's distribution and
> version just by reading the problem description because it was a bug
> introduced by that distributors modifications.
>
> For users of those distribution packages the bug would have been considered
> obvious, despite it not existing for anyone else, especially not the
> developers of the respective applications.
>
> As a developer I wittnessed bugs that were reliably reproducable by myself
> but would not be reproducable on the system of the code's maintainer
> despite sitting right beside me at a developer meeting. Turned out it was a
> specific item in my data set.
>
> Obvious is obviously a relatively relative term.
>

Jes. You are right. I know what you mean. But I'm using Suse (One of the 
biggest KDE Distributions), own absolutely standard hardware and have changed 
nothing in the configuration. As far as I know there are no namable Suse 
backports in Kde 4.2.1.
And all bugs I reported so far were confirmed by the kde devs and have not 
been distribution specific. 
Maybe my main problem is that there have been some bugs in kde 4.2.0 and I 
thought: No problem. They will be fixed in 4.2.1. But for me there has 
happened nearly nothing on the bug front between those releases. 
In my opinion Kde 4.3 just HAS to be much more bug free than kde4 has been 
before. But to ensure that, we have to reconsider some things now and not when 
4.3 is out.

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.