bump version to 1.25

[gitmo/Moose.git] / Changes

diff --git a/Changes b/Changes
index a7a6074..5aab5bb 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,25 +1,96 @@
 Also see Moose::Manual::Delta for more details of, and workarounds
 for, noteworthy changes.
 
-[NEXT]
+1.25 Fri, Apr 1, 2011
+
+  [BUG FIXES]
+
+  * Reinitializing anonymous roles used to accidentally clear out the role's
+    stash in some circumstances. This is now fixed. (doy) (backported from
+    1.9904)
+
+1.24 Tue, Feb 24, 2011
+
+  [BUG FIXES]
+
+  * Reverse the order that Moose::Exporter 'also' exports are dispatched. When
+    trying to re-export from a package that itself exported a modified set of 
+    Moose sugar, you'd get the original Moose sugar instead of the overrides. 
+    There are also now tests for this. (perigrin)
+
+1.23 Sun, Feb 13, 2011
+
+  [PACKAGING FIX]
+
+  * The 1.22 release had a bad MANIFEST. This has been fixed.
+
+1.22 Sun, Feb 13, 2011
+
+  [BUG FIXES]
+
+  * When reinitializing meta objects for classes and roles, we failed to
+    preserve roles and role applications. This led to weird bugs. Many MooseX
+    modules end up reinitializing your class or role. (Dave Rolsky)
+
+1.21 Wed, Nov 24, 2010
+
+  [ENHANCEMENTS]
+
+  * The Support manual has been updated to reflect our new major/minor version
+    policy. (Chris Prather)
+
+  * The Contributing manual has been updated to reflect workflow changes based
+    on this new support policy. (doy)
+
+  [BUG FIXES]
+
+  * The role attribute metaclass did not inherit from Class::MOP::Object,
+    which could cause errors when trying to resolve metaclass compatibility
+    issues. Reported by Daniel Ruoso. (doy)
+
+  * The lazy_build feature was accidentally removed all the docs. Now it's
+    listed in Moose.pm again. (Chris Prather)
+
+1.20 Fri, Nov 19, 2010
+
+  [BUG FIXES]
+
+  * When using native delegations, if an array or hash ref member failed a
+    type constraint check, Moose ended up erroring out with "Can't call method
+    "get_message" on unblessed reference" instead of generating a useful error
+    based on the failed type constraint. Reported by t0m. RT #63113. (Dave
+    Rolsky)
+
+1.19 Tue, Nov 2, 2010
+
+  [BUG FIXES]
+
+  * There was still one place in the code trying to load Test::Exception
+    instead of Test::Fatal. (Karen Etheridge)
+
+
+1.18 Sun, Oct 31, 2010
 
   [ENHANCEMENTS]
 
   * Type constraint objects now have an assert_coerce method which will either
     return a valid value or throw an error. (rjbs)
 
-  * We now warn when an accessor for one attribute ovewrites an accessor for
+  * We now warn when an accessor for one attribute overwrites an accessor for
     another attribute. RT #57510. (Dave Rolsky)
 
   [BUG FIXES]
 
   * The native Array and Hash delegation methods now coerce individual new
-    members, if the _member type_ has a coercion. In other words, if the array
+    members if the _member type_ has a coercion. In other words, if the array
     reference is defined as an ArrayRef[DateTime], and you've defined a
     coercion from Int to DateTime, then pushing an integer via a delegation
     method will coerce the integer to a DateTime object. Reported by Karen
     Etheridge. RT #62351. (Dave Rolsky)
 
+  * An attribute using native delegations did not always properly coerce and
+    type check a lazily set default value. (doy and Dave Rolsky)
+
   * Using a regexp to define delegations for a class which was not yet loaded
     did not actually work, but did not explicitly fail. However, it caused an
     error when the class was loaded later. Reported by Max Kanat-Alexander. RT