From: Jesse Luehrs Date: Tue, 5 Apr 2011 06:34:19 +0000 (-0500) Subject: add some things to ::Delta X-Git-Tag: 2.0000~13 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=6adb18d8cfebe71a69ca36b839c16c7324161ed2;p=gitmo%2FMoose.git add some things to ::Delta --- diff --git a/lib/Moose/Manual/Delta.pod b/lib/Moose/Manual/Delta.pod index e9d42e9..a2c801a 100644 --- a/lib/Moose/Manual/Delta.pod +++ b/lib/Moose/Manual/Delta.pod @@ -18,7 +18,7 @@ feature. If you encounter a problem and have a solution but don't see it documented here, or think we missed an important feature, please send us a patch. -=head1 NEXT +=head1 2.0000 =over 4 @@ -44,6 +44,28 @@ C option, as in: }, ); +=item Class::MOP has been folded into the Moose dist + +Moose and Class::MOP are tightly related enough that they have always had to be +kept pretty closely in step in terms of versions. Making them into a single +dist should simplify the upgrade process for users, as it should no longer be +possible to upgrade one without the other and potentially cause issues. No +functionality has changed, and this should be entirely transparent. + +=item Moose's conflict checking is more robust and useful + +There are two parts to this. The most useful one right now is that Moose will +ship with a C script, which can be run at any point to list the +modules which are installed that conflict with the installed version of Moose. +After upgrading Moose, running C should be sufficient +to ensure that all of the Moose extensions you use will continue to work. + +The other part is that Moose's C file will also specify the +conflicts under the C key. We are working with the Perl toolchain +developers to try to get conflicts support added to CPAN clients, and if/when +that happens, the metadata already exists, and so the conflict checking will +become automatic. + =item Most deprecated APIs/features are slated for removal in Moose 2.0200 Most of the deprecated APIs and features in Moose will start throwing an error