Doc deprecation warnings in Changes for Delta.pod

diff --git a/Changes b/Changes
index 5eade26..53bfcb3 100644 (file)
--- a/Changes
+++ b/Changes
@@ -13,6 +13,13 @@ for, noteworthy changes.
   * Removed the long-deprecated Moose::Meta::Role->alias_method metohd. (Dave
     Rolsky).
 
+  * All features which have been declared deprecated now issue a warning using
+    Moose::Deprecated. Warnings are issued once per calling package, not
+    repeatedly. See Moose::Deprecated for information on how you can shut
+    these warnings up entirely. Note that deprecated features will eventually
+    be removed, so shutting up the warnings may not be the best idea. (Dave
+    Rolsky)
+
   [NEW FEATURES]
 
   * We no longer unimport strict and warnings when Moose, Moose::Role, or

diff --git a/lib/Moose/Manual/Delta.pod b/lib/Moose/Manual/Delta.pod
index 5786f6a..91634c2 100644 (file)
--- a/lib/Moose/Manual/Delta.pod
+++ b/lib/Moose/Manual/Delta.pod
@@ -20,6 +20,14 @@ send us a patch.
 
 =over 4
 
+=item All deprecated features now warn
+
+Previously, deprecation mostly consisted of simply saying "X is deprecated" in
+the Changes file. We were not very consistent about actually warning. Now, all
+deprecated features still present in Moose actually give a warning. The
+warning is issued once per calling package. See L<Moose::Deprecated> for more
+details.
+
 =item You cannot pass C<< coerce => 1 >> unless the attribute's type constraint has a coercion
 
 Previously, this was accepted, and it sort of worked, except that if you