Move to Test2::V0
Can't locate MooseX/StrictConstructor.pm in @INC
sf#7 fixing missing libs
sf#7 fix missing library
Can't locate MooseX/StrictConstructor.pm in @INC
Dist::Zilla improvements
Dist::Zilla improvements
sf#7 fixing min version issue
Dist::Zilla improvements
working on as same as https://rt.cpan.org/Ticket/Display.html?id=98148
sf#7 removing unused libs and fixing version
sf#7 dist::zilla improvements for versioning
Tagging the 1.1 release
#10 fixing pod issues
#10 fixing copyright dates
MooseX::Method::Signatures deprecation issues
Done
#10 - removing dependency on deprecated method signatures module
MooseX::Method::Signatures deprecation issues
Building on my machine, annoying the core signatures don't support the Moose method validation. Going to try to add that in for a little.
Auto-generate cash entries
Think it's done but I don't have sentinel benefits anymore, so just keeping perl deps up to date
MooseX::Method::Signatures deprecation issues
Dist::Zilla improvements
I think this is done in 1.0, but check . . .
New moose breaks code
Header lines not reading correctly
Moose deprecation warnings
Adding 1.0 dist
Updating dist.ini for new Dist::Zilla
Updating dist.ini for new Dist::Zilla
Tagging 1.0 release
Fixing bug #6, moose deprecation warnings
But, both together does.
Header lines not reading correctly
Fixed in r32
Fixing bug #5, headers can be read/written out ...
Also open an RT ticket for this.
Essentially, I'm testing for order in the output, but I don't think order is actually...
Also looks like https://rt.cpan.org/Public/Bug/Display.html?id=88530 should fix it,...
https://rt.cpan.org/Public/Bug/Display.html?id=90983 suggests it should be fixed...
Moose deprecation warnings
New moose breaks code
Checked in r31.
Fixing bug #4, new moose breaks code
Header lines not reading correctly
Updating dist.ini with modern libraries
New moose breaks code
New moose breaks code