Going for the Full Monti (Re: How to improve Squeak)

Doug Way dway at mailcan.com
Mon Jul 12 05:08:58 UTC 2004


Off the top of my head this sounds like a good amount of work, and I 
don't want to get stuck doing most or even half of it. ;)  But it may 
be the right thing to do.

I guess we should brainstorm a bit on how this might work before making 
a decision, of course.  Erm, would the "image" be a giant single 
package in Monticello?  Or at least the part of the basic image which 
is not already split into other packages... which would still be a 
pretty giant package at this point.

And then how would the update stream fit into this, if at all.  It 
would appear that the core committers would not need an update stream, 
at least.  Maybe there would still be an update stream for the "public" 
alpha image somehow.

- Doug


On Sunday, July 11, 2004, at 07:25 PM, goran.krampe at bluefish.se wrote:

> Hi people!
>
> Marcus Denker <denker at iam.unibe.ch> wrote:
>> To come back to the example: Don't forget that we strike for a "fast
>> moving agile" process.
>
> Yes, and I think we should really sit down and try to set up Monticello
> for managing the image. Avi has already done some experiments. Then we
> should of course have limited "commit" access to that.
>
> This way we can have BFAV for the contributions coming in (like patches
> in other open source projects) and we can go straight to Monticello for
> other stuff.
>
> Such a model would help A LOT I think but it will demand two things of
> developers with such commit access:
>
> 1. Test it locally first. Don't commit stuff that is half baked. This 
> is
> basic stuff for working in an open source project of course. In the
> Mozilla project they say that the "tree is on fire" when someone does
> that.
>
> 2. Write proper commit notes (= commit comment in CVS). Those will be
> critical in knowing what has been done and for us to be able to produce
> ChangeLogs.
>
> I think perhaps if we do this step first - then we can more easily pick
> up the TFNR goals again. It will be easier to perform those things when
> we have a "full Monticello" working.
>
> Avi? Comments? Is Monticello up to the task? :)
>
> regards, Göran
>




More information about the Squeak-dev mailing list