[Seaside] So where is the "release" version of 3.7?

[Todd Blanchard]

Progress is all well and good, but in a cycle you typically have open  
development - stuff is broken all over the place, not everything  
planned is done.  This is usually 'alpha'.

At some point you reach "feature complete"  but with known problems.   
This is usually 'beta'.  From here you commit to no more new  
features, no structural changes, only bug fixes.  Features and  
architecture are frozen.

When the defect discovery rate gets low enough, you call it a  
release.  You may have subsequent minor releases to fix minor  
problems - but this version is considered "stable".  I can count on  
it being of reasonably high quality and that pulling an update of  
this line will not require any code changes on my part.

Then you start over.

I know that the feature freeze/bug fix only releases aren't really  
fun and you have to restrain your muse.  But for the people trying to  
build on top of this stuff - your fun comes at their expense.  They  
don't have time to change a bunch of code just because in some  
iteration the framework developers decided to toss some mechanism  
because it isn't elegant.

Draw a line in the sand - call it the stable release, we can have an  
announcement, serve cake, get on slashdot.  Bump the version number.

If people can't see what horse to bet on, they will not bet.

-Todd Blanchard


On Feb 26, 2007, at 10:07 AM, Damien Cassou wrote:

> 2007/2/26, Boris Popov <boris at deepcovelabs.com>:
>> Definitely don't want to see the same run-and-gun that's happening in
>> Squeak overall :) Progress is good, but being a little more organized
>> and explicit about what each version means would be great.
>
> What would you suggest that keeps Lukas, Philippe and Michel
> productive and inventive?
>
> -- 
> Damien Cassou
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside