New release-plan

David Nolden zwabel at googlemail.com
Fri Nov 27 21:53:19 UTC 2009


Am Freitag 27 November 2009 22:32:45 schrieb Alexander Dymo:
>
> Which usually means _never_ release.
> 
> I personally think that:
> 
> 1) The direction Andreas took (to remove all unfinished/not working stuff)
>  is the only right way to do the release
> 
> 2) We need to release now. KDevelop is a big project, you will always want
>  to "finish" things here and there. 1 month of delay won't change anything
>  in this respect
> 
> 3) We need to face the fact, 4.0 release will suck anyway. It won't be
>  feature complete and it won't work well. Remember, 3.0 wasn't that good
>  either. It's 3.1 release which was really good.
But I won't participate in that suckage. Why do we need to do it? It gains us 
nothing. I hate that KDE4 has done it that way..

I don't expect the release to be feature-complete, but a basic set of properly 
working features should be there, else we don't even need to bother releasing 
it. Why call something "4.0" if it really is a beta?

> 4) To stabilize, let's continue to throw out and disable features. That's
>  not as bad as you, guys think. Commercial software development has taught
>  me that people can live without surprising amount of features, just as
>  long as your app doesn't crash ;)

It is a consensus that we don't want unstable features. If a non-critical 
feature is unstable and not well maintained, then it is fine to remove it. 
However I, and some others, consider the source-formatter stuff a critical 
feature, which should be fixed (in any way) instead of removed.

Greetings, David




More information about the KDevelop-devel mailing list