Linked by Thom Holwerda on Tue 29th Jul 2008 20:39 UTC, submitted by vege
Thread beginning with comment 324980
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.
RE[3]: Don't look back
by google_ninja on Thu 31st Jul 2008 03:04
in reply to "RE[2]: Don't look back"
The paradox is that without the KDE developers setting 4.0 in stone and working off from it, 4.1 would probably not have happened and certainly wouldn't be as good as it has turned out to be.
That is silly. The only reason that would be the case is if the kde core developers have no communication at all with the developers working on the platform. Since all the mailing lists are open, we know that isn't true. KDE4 was a milestone, not a release. The only reason they made it a release is because they were already late, and didn't want to look bad by waiting another 7 months to do it right.
"The paradox is that without the KDE developers setting 4.0 in stone and working off from it, 4.1 would probably not have happened and certainly wouldn't be as good as it has turned out to be.
That is silly. The only reason that would be the case is if the kde core developers have no communication at all with the developers working on the platform. Since all the mailing lists are open, we know that isn't true. KDE4 was a milestone, not a release. The only reason they made it a release is because they were already late, and didn't want to look bad by waiting another 7 months to do it right. " Releasing of open source software doesn't work like that, it is NOT commercial software.
Perhaps some references might explain it a bit for you:
http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar...
http://radio.weblogs.com/0103807/stories/2002/12/01/understandingTh...
"If you are an ex-commercial developer then you want desperately to reach a "1.0" stage or a "near functional", "mostly baked" stage before going live. You wouldn't want to release something piece meal, would you? After all -- that's the way it's done.
Actually no. In the Open Source world, that's not how it's done."
This is not a new concept for open source:
http://www.google.com.au/search?hl=en&q=%22release+early+releas...
45,200 hits for the open source catchcry phrase that applies here ... "release early, release often".
That is silly. The only reason that would be the case is if the kde core developers have no communication at all with the developers working on the platform.
News at 11. Software works better in a release early and release often fashion. When you've achieved what you want to achieve in the run up to a release, release it and build off that. That is the certainly the way open source development works, and the way even commercial companies work.
The only reason they made it a release is because they were already late, and didn't want to look bad by waiting another 7 months to do it right.
I'm afraid you don't get to decide the requirements for a release. The KDE developers do. If it doesn't work for you then don't use it, and distributors generally make that decision for you by deciding whether to ship it by default. That's the way releasing open source software has always worked.
You can't have release candidates forever, otherwise if they'd waited nine months to release KDE 4.0 they would have had ten times the problems and everybody would have complained bitterly that it wasn't good enough for them anyway.
For some people 4.1 will work great. For others 4.2 or 4.3 will only be good enough as more applications get ported to the platform. There is no black and white.







Member since:
2005-07-06
The paradox is that without the KDE developers setting 4.0 in stone and working off from it, 4.1 would probably not have happened and certainly wouldn't be as good as it has turned out to be.
Still some gaps to fill in and new functionality to be added, but you can really see where they've been heading with it now.