From: Dave Rolsky Date: Tue, 9 Feb 2010 15:54:05 +0000 (-0600) Subject: Update deprecation policy to match current reality X-Git-Tag: 0.97~4 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9f41127cc577d387a3610a38b7dc20cf269f3a6f;p=gitmo%2FMoose.git Update deprecation policy to match current reality --- diff --git a/lib/Moose/Manual/Contributing.pod b/lib/Moose/Manual/Contributing.pod index c4e12b3..05a8e5a 100644 --- a/lib/Moose/Manual/Contributing.pod +++ b/lib/Moose/Manual/Contributing.pod @@ -383,8 +383,11 @@ B do I one deprecation cycle (more if it is larger change). For really larger or radical changes dev releases may be needed as well (the Cabal will decide on this on a case-per-case basis). -The preference with regard to deprecation is to warn loudly and often so that -users will have time to fix their usages. +Our policy with deprecation is that each deprecation should go through several +stages. First, we simply add a deprecation notice the documentation in +F and L. In a future release, we then make the +deprecated feature warn loudly and often so that users will have time to fix +their usages. Finally, the feature is removed in a later release. All backwards incompatible changes B be documented in L. Make sure to document any useful tips or workarounds