On Thursday 08 March 2007 19:23, Dominik Haumann wrote: > On Thursday 08 March 2007, Aaron J. Seigo wrote: > > > KDE 4.0 will be reviewed as a Vista competitor, > > > > that's a marketing issue, and the key is expectation management and clear > > communication about how the development process works. > > > > > and it would make a > > > disastrous impression if core elements of the user interface are either > > > not present yet or have an extremely bad usability because of a rushed > > > schedule. It would also make a disastrous impression if important > > > desktop applications (e.g. kdepim) are missing from the KDE 4.0 end > > > user release. > > > > it could be disastrous if we try and tell the world that 4.0 is The > > Release To End All Releases. it doesn't need to be disastrous if we > > communicate the difference and relationship between KDE4 and the 4.0 > > release milestone. > > this is a very important point Stephan Binner already brought up in his > blog 'Disambiguation "KDE 4", did you mean "KDE 4.0"?' - see also: > http://www.kdedevelopers.org/node/2600 > > KDE4 != KDE4.0 > very few (users?) are aware of this I fear :)
That's why it is even more important to make sure that KDE4.0 is not a change for the worse compared to 3.5.6. Apart from bug fixing sessions, I'd really appreciate dedicated usability bug fixing sessions for the base system and the major applications. A policy to allow (smaller) usability changes in a certain period after feature freeze (and regular updates of precompiled kde for the usability people ;-) ) would sure be beneficial. Otherwise I agree that the big plans we've had for KDE4 are meant for the life cycle, not the first release. /el -- Ellen Reitmayr KDE Usability Project usability.kde.org
pgpNKCNA43OeI.pgp
Description: PGP signature
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
