[squeak-dev] Deprecation policy

Ken Causey ken at kencausey.com
Fri Jul 3 21:41:11 UTC 2009


I would like to suggest that we develop a formal deprecation policy.  It
could be as simple as deprecate in one release, remove in the next.  I
just think we need to be consistent about it and remove no individual
methods without following it.  How this relates to the idea of
repackaging and removing whole categories of classes, I'm not so sure.

Ken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090703/6fb2a02b/attachment.pgp


More information about the Squeak-dev mailing list