I think that any large amount of work that can rapidly rot should be 
pushed into 3.9 or current unstable version.
Else you will get frustrated.  But I'm a bit extreme on that :) (a KCP 
guy talking).


>
> Hi Folks,
>
> The first part of the MorphicSplitters project is basically 
> PackgeInfo, i.e. reclassification of stuff. Very little methods were 
> actually modified, and they sould not generate any problems.
>
> But if we wait until 4.1 to get the work in, we'll have to re-check 
> any Morphic or Etoys stuff that is modified during that time. This is 
> especially true for any ToolBuilder stuff.
>
> So I prefer to get this first MorphicSplitters stuff in 3.9, to serve 
> as a base to other efforts, most important ToolBuilder.
> At some time, MorphicSplitters will need actual refactoring to remove 
> bad dependencies between BaseSqueak and CoreMorphic and between 
> CoreMorphic and FullMorphic/Etoys. The first of these (BaseSqueak -> 
> CoreMorphic) is also needed for ToolBuilder. So, we'll have to 
> coordinate that work. That will be much easier if we start from the 
> same base. This means, please start serious ToolBuilder refactoring 
> with as much as MorphicSplitters in as possible.
>
> Cees, Dan, do you agree?
>
> Cheers,
> Juan
>
> ----- Original Message ----- From: "Cees de Groot" <cg at cdegroot.com>
> To: "The general-purpose Squeak developers list" 
> <squeak-dev at lists.squeakfoundation.org>
> Sent: Friday, April 01, 2005 11:26 AM
> Subject: Re: Unofficial status report
>
>
>> On Fri, 1 Apr 2005 14:57:05 +0100, <goran.krampe at bluefish.se> wrote:
>>> 4.1 = This will then be the release with the result from
>>> MorphicSplitters and thus we are buying them a little bit more time. 
>>> The
>>> plan was to push that stuff in as the first thing and if we open the
>>> alpha stream of 4.1 after release of 4.0 then that would mean... say 
>>> 1st
>>> august? What do the splitters say about that? Sounds doable?
>>>
>> Doable, yes. But the MorphicSplitters work will result in LARGE 
>> changes (the .mcz files are around 2.5Mb together - we're dealing 
>> with a huge chunk of code here), so putting it in 4.1 will result in 
>> a large changes file needing to be distributed with all of the 4.x 
>> series...
>>
>
>