FWIW, change sets have long (always?) sent #initialize to classes when that method was changed. Seems like a useful feature.


On 7/29/13 12:09 PM, Chris Cunningham wrote:
I don't/didn't think that #initialize was called on a package load unless the class was a new class - so that it wouldn't overwrite accumulated state since the initial load.  Isn't that still the case?

worth testing in any case.