>
>
> What about concurrent changes between contributors ?
> Say I changed a private method A that Levente removes.
> That's where MC shines.

The cycle consists of... check out slices and packages from the repo,  
build one or more images, export slices to source, check in code to  
repo.

So you have SCM tools working on the important source files to tell  
you what has changed or what has conflicted. It is not as good at  
diffing mcz packages since they are zip files, but it does ok on a  
method level in an st file.

Secondly you can take someone else's image, import the slice  
definitions to it, and the Export doCheck will tell you what has  
changed in their image relative to the slices exported from yours.


Keith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20100311/8aeb850c/attachment.htm