Welcome to the new Moose blog, where we blog about Moose and MooseX and anything else of relevance.
We'll be using this blog to announce interesting Moose projects, upcoming API changes and deprecations, and maybe to write fascinating articles about Moose (enthusiasm and energy permitting).
I've just released Moose 1.09, which includes a number of changes. Notable, this release includes an API change or two, as well as a whole bunch of deprecation warnings.
For a long time, we've been saying that features are deprecated in the Changes file, but not actually changing the code. With Moose 1.09, every feature that's been marked deprecated in the past couple years now issues a warning. To make the warnings less intrusive, I wrote a new package called Package::DeprecationManager. This module manages the deprecation warnings and ensures that a given warning only shows up once per package. This should avoid any "I upgraded and now my logs filled my disk" disasters.
Actually warning about deprecated features is the first step towards removing them in the future, so please address any warnings you see in your own code.
A number of MooseX modules will trigger these warnings. In many cases, we were able to help the CPAN authors update their code, and we added a conflict warning to the Makefile.PL, so please look out for the conflict warning. However, in the interest of getting code released, not every MooseX module has been updated. If you are using a module which now warns, please file a bug for that module. MooseX module authors, the fixes are generally very simple. If you have question, please just us in the #moose-dev IRC channel or send email to the Moose mailing list.