Yet another failed KDE release?
rainofchaos at gmail.com
Sun Mar 24 12:44:12 GMT 2013
2013/3/24 dE . <de.techno at gmail.com>:
> On Fri, Mar 22, 2013 at 4:08 PM, Myriam Schweingruber <myriam at kde.org>
>> Hi Nikos,
>> On Fri, Mar 22, 2013 at 8:08 AM, Nikos Chantziaras <realnc at gmail.com>
>> > On 19/03/13 18:58, dE . wrote:
>> >> This release of KDE (4.10.1), is till date the buggiest I've seen.
>> > They've all been, in my case. Not serious crasher bugs, but glitches
>> > everywhere. Of the very annoying, hair-pulling sort. I did report all
>> > of
>> > them, but no one cares though.
>> > The biggest issue is that with each new release, there's more glitches
>> > while
>> > the old ones are still there. They accumulate over time. There doesn't
>> > seem to be any stabilization going on with KDE. It's always a race to
>> > the
>> > next major version.
>> Again, you are concluding from your experience to the general one.
>> Please give me the bug reports so I can counter check. And make sure
>> you ALWAYS test with a new user or move the old config files elsewhere
>> when you do a major upgrade.
>> Regards, myriam
> If everyone's concluding the same way, there's something wrong with your
> Also it doesn't appear to be a to be a coincidence, that only KDE team
> members don't complain, and trying to defend the user's argument. The user
> is the only one speaking the real thing, and their opinion should be
> Their argument should never be cut, instead more information should be
> Why dont you KDE people realized, that there're computer users out there,
> who, after realizing the HUGE no. of bugs in one distro (using KDE as
> default), will switch to another one without complaining? They almost the
> whole of the KDE userbase.
This user vs your KDE (dev) people seperation make me feel really bad.
There is actually just a KDE community in which users build their own
system. Most of contributors are just normal KDE users who devote
their free time to make KDE better without any pay. So when they do
have free time, they will use it to fix the bug which is the most
annoyance to themself. This is the characteristics of open source
projects without a company backing it.
So if you want to have a bug fixed, the fastest way is by fixing it
yourself. If you do not have time or skill, provide enough information
and show people the bug is important. Convince they to spend their
free time to fix it. Blame the whole KDE community is not the way out.
> Even Linus quit cause of too many bugs, and you still don't believe it.
> Here, I'll give some e.gs --
> This's a confirmed Debian bug; that commenter didn't know I confirmed it on
> Gentoo first, then reported it.
> Just look at this in general --
> 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.
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde