Strange behavior

Cees De Groot cdegroot at gmail.com
Sat Oct 22 19:28:58 UTC 2005


On 10/22/05, Marcus Denker <denker at iam.unibe.ch> wrote:
> An image build in a way that we don't need to replace in in the
> future, and build by taking the last one "load updates" and be done.
>
Ok, so the update stream lives on.

> One of the problems right now is that the image is around 20MB large
> after loading the latest from the repostory...
>
That issue was fixed - dunnow whether it's in some version of the
code. but even I remembered that mail passing by:

McHttpRepository>>flushCache
   super flushCache.
   readerCache := nil

brings my post-PlusTools back to <<20Mb

> I am not up to speed with harvesting, so I everything need to be taken
> a bit with a "I need to check that". But the problem with Traits is that
> it changes the system in a way that can't be merged with Monticello.
>
So let them publish an image and work from there?

I'm fine either way, but then at the very least I want a big red
trafficlight on the frontpage on whatever website that signals "please
do not do ANY work on 3.9a until Traits is in, because it'll be
worthless".

Not money, but unclear communication is the root of all evil :)

> Ok. Back when harvesting was done with changesets and nobody cared
> too much, we had a good reaction time in some cases... but mostly,
> reaction
> time was *months* even for stuff like typos in class comments.
>
Yup. And we complained about that, and we set about making it better -
and I'm quite confident that we're on the correct path. If there are
hurdles on the road, fine. But I think that the 3.9a team must then
immediately pull the brakes (on squeak-dev, at least), tell everyone
to stop what they're doing, and wait for event X to happen.



More information about the Squeak-dev mailing list