Hi, I would like to ask if the current solution where the method Object>>#deprecated: is placed in the package Deprecated14, is good. For images where this package is not present (e.g. Pharo-Kernel) we got unimplemented call and possible DNU. The method #deprecated:on:in: is in the kernel. Of course if you do not have deprecated code in the image then call of it should raise error. However some external packages (and some internal packages like Zinc) do not have deprecated code in separate package and do use #deprecated: for deprecation warnings. Because #deprecated: is bound to Pharo version, I think it would be better solution to have a message named pharoDeprecated: that will be called from Pharo packages that will be placed in Deprecated14 package and then have #deprecated: message placed in the kernel that will be used by external packages. Cheers, -- Pavel