Linked by Thom Holwerda on Thu 27th Nov 2008 21:45 UTC, submitted by lemur2
The KDE team has released the first beta of KDE 4.2, slated for release coming January. Quite a lot of new features have been added, as well as lots of bug fixes and performance improvements. This release also makes a lot of strides to feature parity with KDE 3.x, by adding those small little features that KDE 3.x users are barely aware of, but which were missed in KDE 4.0/4.1, such as taskbar grouping, multiple rows in the taskbar, panel auto-hiding, a traditional icon desktop through 'full-screen' foderview, and so on.
Thread beginning with comment 338569
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2007-11-17
I guess it is safe to assume, that steve grasps the concepts behind the cathedral and the bazaar.
What we are still discussing is, whether a project
a.) is allowd to formulate a set of (probably non-traditional) milestones
b.) optionally change/adapt/reformulate this milestones during development
c.) communicate the (final) requirements, feature matrices, etc. resulting from these milestones
d.) release the software when they *think* they have reached the required level of completeness and
e.) slap a label like "4.0" on the resulting code / product / whatever.
KDE 4.0 was communicated to "eat your children". KDE 4.1 was released backgrounded by "early adopters can now start to switch to it for everyday work". I don't think that we should mandate all (FOSS) projects have to agree on the same criteria for major releases.
EDIT: Just in case this was not clear from my comment:
I think the KDE devs did the right thing to get the thing out of the door early. And I have dealed with too many .0 releases in the past to have any illusions left about "if its .0, it is gold".
Edited 2008-11-28 11:06 UTC