>
>> One of the deliverables with 3dot9 final should be a
>> 3.10 with all changes from 3.0.
>>
>
> This is not possible because of two reasons:
> 	- the MC based process is broken, we can't load from 3.0
> 	  to get 3.9beta. Yes, bad. I am taking full responsibility.

I'm too.
I invite everybody to build something and we will use it.

>           (We have the complete code history, though. Just not  
> easily loadable)
>  	- The changes file would hit the 32MB limite before you would get
> 	  a complete 39beta even if it would work in theory.
>
> Besides keeping the source, I'm sure you would want to keep
> the changeset information, too. Cost: 5MB of image size for 3.9 alone.
>
> So just for a 3.9 with all changes, all in all we are talking about
> 30MB that nobody needs but system developers. Do we *really*
> want to ship that to all the users?
>
> The history mechanism of Squeak does not scale anyway. Why
> only ship the history from 3.0? why not the *complete* history? What
> do you do in 10 years? 7MB left in the changeset is kind of small...
>
> The whole history mechanism of Squeak does not scale: There
> is no need at all to have the old versions on the local disc at all.
> What we need is a server that has the complete history that
> then can be queried from the clients, everthing else makes
> no sense.
>
> For now, we should keep of course the latest beta version with the  
> history of
> 3.9 available. Just that it's not called "3.9", but "3.9 dev" or  
> something
> like that.
>
> And we should get a student to work on that code history project...
>
>        Marcus