In MC1 version history is tightly coupled to package structure. In MC2, version history is associated with the code, not its organization, which means that you can reorganize the code without losing the history. Further, you can have different organizational schema operating at the same time. For example, one developer can organize things into packages, while another uses change sets, and they can still use MC2 to do merges. MC2 its self is organized into a set of packages, but I use UnionSlices to bundle them up into a single snapshot for release. Colin
This is the killer app for me :)
For me too. Slices can be files in GNU Smalltalk, which is absolutely cool; it can provide the way to check out code from the image to files. Thanks very much for Monticello!
Paolo