Linked by Thom Holwerda on Tue 27th Jan 2009 18:41 UTC
KDE The release of KDE 4.0 was not a smooth one, and left a number of users a bit disgruntled. Still, the release showed so much potential that it was oozing out of every pixel. KDE 4.1 improved significantly in many areas of concern, but it wasn't yet ready for everyone. With today's release of KDE 4.2, the KDE4 vision is ready to face not only developers and enthusiasts, but every users. We have taken a look at the release candidate for KDE 4.2, and we have a short interview with KDE's Aaron Seigo.
Thread beginning with comment 346377
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: FLAME ON!
by Daniel Borgmann on Sat 31st Jan 2009 15:51 UTC in reply to "RE[3]: FLAME ON!"
Daniel Borgmann
Member since:
2005-07-08

"(the only exception being 1.0)"

Which was my point. And no, GNOME 2.0 was not meant to be an unstable release, there has been a separate branch for this purpose (I believe it was 1.99 or something like that). Yes, .0 releases always tend to be unstable (GNOME 2.0 definitely was) because they are young, all I am saying is that I find it counter-intuitive and rather misguiding to assign a different meaning to 1.0 than to every other .0 release.

Reply Parent Score: 2

RE[5]: FLAME ON!
by PandaMine on Sun 1st Feb 2009 00:04 in reply to "RE[4]: FLAME ON!"
PandaMine Member since:
2009-01-29

The main reason why is that 1.0's are often seen as the first non alpha/beta release of a product, so they at least want the software product to be stable.

First impressions count, even in the software world, and if the first release of a product is very unstable or unusable it gets a bad reputation which is very hard to clear (even if you do fix the problems.

Reply Parent Score: 1