So there's a new release of Catalyst on CPAN. Go check it out!
Highlights include the long delayed removal of regular expression dispatching in actions, bug fixes for people using fast cgi and plack, documention updates and more.
This closes the Zombie - Boomstick development cycle. So how did we do? Lets review the orginal play perl quest list:
Mirror Important Perl Projects from Shadowgit to Github Catalyst Org: Complete! Thanks to mst and everyone that assisted in this! If you don't see a repository on http://github.com/perl-catalyst that you want, give us a shout out and we'll try to add it to the mirror.
Travis CI Testing on Github Org: Complete! Already handy for helping me review pull requests
Remove Regexp dispatching from core and create a stand alone distribution for backwards compatibility: Done!
Fix broken PSGI Logger for FCGI: Done!
Coring the Unicode Plugin: Some work on this was done, but is incomplete and we'll just have to hack on this for the next development cycle. Thanks to everyone that contributed to shaping the discussion on this!
Core support for RESTful Content Negotiation: This task has been move to prototype status, as although it appears to be something people want, its not at all clear what the minimum useful features would be. See mentioned links to prototype application below.
Core support for action level POST/PUT HTTP request body parsing: There is a prototype for this (see prototype discussion below) but I do not believe the prototype is sufficiently non trivial for us to decide if the approach is correct.
Application Prototyping: Incomplete. I started a prototype application based on modeling a basic TODO type application (which seems to have become the helloworld example of today) which I believe would represent an application that was both simple and yet non trivial enough to rationally expose basic flaws in any approach to new ideas we wish to have in Catalyst. I firmly believe that coding shoul be to a use case, not in theory, so I think having a strong prototype example we can use now and in the future for experimenting with various new ideas we wish to bring to the framework would be highly beneficial. This application prototype probably needs it own task lists and test case in order to complete it enough where it can be a good use case example.
Feel free to checkout and play with (or contribute to) the existing prototype, which I will blog about next week!