| |||||||||||||
|
| |||||||||||||
KOffice 2.1 releasedKOffice 2.1 releasedPosted Nov 25, 2009 9:47 UTC (Wed) by eru (subscriber, #2753)In reply to: KOffice 2.1 released by michaeljt Parent article: KOffice 2.1 released I think the linked-to release note honestly made clear this is not yet ready for prime time. Many features are still missing or limited, and expected in 2.2 or 2.3. So comparing this to the quite mature OOo would not be fair.
(Log in to post comments)
KOffice 2.1 released Posted Nov 25, 2009 9:57 UTC (Wed) by michaeljt (subscriber, #39183) [Link]
Please, I'm not looking for an excuse to bash either of them, I'm just interested in KOffice's progress :)
KOffice 2.1 released Posted Nov 25, 2009 18:57 UTC (Wed) by xorbe (subscriber, #3165) [Link]
sounds like the KDE mindset in general these days.
KOffice 2.1 released Posted Nov 26, 2009 2:15 UTC (Thu) by aseigo (guest, #18394) [Link]
What, release early and release often? That's the open source methodology, something some people seem to have forgotten around here. Sadly.
KOffice 2.1 released Posted Nov 26, 2009 8:56 UTC (Thu) by michaeljt (subscriber, #39183) [Link]
> What, release early and release often? That's the open source methodology [...]
Unfortunately it doesn't seem to be that simple once a project passes a certain size. Too many people just refuse to touch the code until they deem it stable unless the coolness factor of some of the new features outweighs.
I'm not so arrogant as to pretend I have a brilliant solution where cleverer minds than mine stumble. The only thing I can think of is to modularise aggressively, so that people can use stable code overall and still try out those (little) bits of the development code that especially interest them - and hope that most of the development code will end up being covered and tested.
I think this is something that might apply to testing versions of distributions too, if you substitute package with module.
|
|
||||||||||||