[Seaside] monticello remote repositories

[Stephen Pair]

You're quite right.

When I was coordinating the release of a product that was one of about 5
products that had a shared code base and a total of about 40 Smalltalk
developers, merging was a big effort and Envy didn't make it easy.  That
was the motivation for the merge tool that we built for ObjectStudio.

Since I don't know of any Squeak projects that come even close to this
scale, having a merge tool (while nice) doesn't seem like it would be
worth devoting a lot of time to developing at this point.

However, I hate telling people that they should or shouldn't do
something...so if anyone does develop a merge tool, I would certainly
not complain.

- Stephen

> -----Original Message-----
> From: seaside-admin@lists.squeakfoundation.org 
> [mailto:seaside-admin@lists.squeakfoundation.org] On Behalf 
> Of Avi Bryant
> Sent: Monday, December 30, 2002 6:11 PM
> To: seaside@lists.squeakfoundation.org
> Subject: Re: [Seaside] monticello remote repositories
> 
> 
> 
> [snip lots of discussion about merging]
> 
> It's great to see interest on Monticello, but it seems to me 
> that there's a *lot* of work that's higher priority than 
> merging method text - as Andreas pointed out, individual 
> methods are generally small enough that on the odd occasion 
> that you do change one simultaneously to someone else, 
> resolving the conflicts by hand should not be laborious.
> 
> It's been a while since I've spent any time on it, but the 
> last spurt of activity was aimed at allowing branching and 
> distributed repositories.  If anyone's interested in 
> contributing to Monticello, it would be really great to get 
> that work finished up before we worry about anything else.
> 
> Avi
> 
> _______________________________________________
> Seaside mailing list
> Seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>