Matthew Fulmer wrote:
>> * When you have system methods that are modified during load and rely on 
>> new methods in the package. This is by far the biggest issue (and a 
>> problem even with Change Sets). For example, 
>> http://bugs.squeak.org/view.php?id=6535 contains a change to 
>> OrderedCollection>>copyFrom:to: which utilizes postCopyFrom:to: that is 
>> defined in the same place. In change sets you can at least manually 
>> reorder the methods. Monticello does it unpredictably so it may work for 
>> one person and not for another (I wish MC would load methods in a 
>> well-defined order).
> 
> This is never a problem in MC1.6, period. 

Wow. This sounds like an excellent reason to switch to MC 1.6 since this 
has been a constant nightmare in the back of my for dealing with 
incremental updates. Is 1.6 ready for wide-spread use?

Cheers,
   - Andreas