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 (file)
--- a/lib/Moose/Manual/Contributing.pod
+++ b/lib/Moose/Manual/Contributing.pod
@@ -383,8 +383,11 @@ B<must> do I<at least> 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<Changes> and L<Moose::Manual::Delta>. 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<must> be documented in
 L<Moose::Manual::Delta>. Make sure to document any useful tips or workarounds