What, a Catalyst release already? Didn't we just announce the start of the Northern Hemisphere summer (or Southern Hemisphere winter, your call) development cycle? Yes, we did, but unlike in previous releases where we hacked for 2 months or so and then dropped a load of stuff all at once, this time we are going to make releases as individual quests for the development cycle is completed. That way we can start to gather CPAN testers results as well as get early release code into YOUR hands so that you can poke, play and be creative with it. Or complain (ideally you'd have complained before, we the quests were being proposed, but maybe you didn't notice, or you thought I was just joking about doing this stuff...)
This is a development release and although all tests seem to pass and we've met minimal goals, at the least, we reserve the right to change anything and everything up to the stable release, targeted for end of September / early October 2013. So play with it, but hesitate to send this to production (unless you are willing to bear the consequences). Think of this as your second chance to review important changes to Catalyst and comment / contribute / complain.
Quests released in this first development version:
Makefile.PL dependencies need updating
http://questhub.io/realm/perl/quest/51dece1605581e3520000008
This release meets the minimal goal of updating the module mst pointed out, which prompted this quest. However I will leave it open since there's still room for someone to take charge of reviewing the Makefile.PL for sanity.
This change should help with any problems you may be having installing Catalyst onto Perl 5.18+
PSGI Middleware
http://questhub.io/realm/perl/quest/51d714894de22b0d7c00004a
You may now declare PSGI middleware via configuration, under the configuration key 'psgi_middleware'. This give you a new option when configuring your PSGI middleware, which should make it easier to properly couple middleware to your application (and make it possible to leverage Catalyst's powerful configuration capacities to customize and control your middleware.
Although working on this taught me tons about how the Catalyst request / response cycle works, it left me wondering dangerous thoughts (like, should the entire Catalyst application be composed of middleware, or middleware wrappers on stand alone classes...) More on that speculation another time.
There's tons more we could do here, but we met our goal for this, and I will consider the quest closed (changes for bugs or regressions only for this development cycle).
Don't worry, there's tons more chances for you to jump in and close a quest, thereby earning immortalization (insofar as git history is immortal). Take a look at the blog announcing the Hamburg development cycle for more on what we are doing and how to help. Or just go right to the Hamburg quest list on quest hub:
http://questhub.io/realm/perl/explore/latest/tag/hamburg
Even if you can't contribute, you can at least try to install this development release and see how it runs with your app. That's very easy:
cpanm Catalyst --dev
Good day to you all.
Comments