Göran Krampe wrote:
> Ok, here is a suggestion:
> 
> - We add a Change object that is DSClassInitializationChange. So Igor is 
> right in a sense, better to put the developer in full control. This 
> change could just list a bunch of class names that it will send 
> initialize to - in that order.
> 
> - Thus the developer can edit/add such a change as needed.
> 
> - And we add some predictable logic to cover 95% of the cases by auto 
> creating such a change.

Works for me.

> Given what Andreas said in the beginning about how class initialization 
> should be handled on revert, perhaps it gets tricky. I need to read that 
> again...

Don't worry too much about it. I don't think that this is the most 
critical aspect here and I'd much rather have something to play with 
sooner ;-)

Cheers,
   - Andreas