X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=Changes;h=3c2d211257e6921f3791141d3a923b9191148ca5;hb=63a50bd691370dbe53aea733ef44f34d5e4e8f06;hp=fbbd97f96b79c845adf5dfa001dc5c9e75ea9809;hpb=0d47e0404be82f525100b303c07e4acd14c6fea5;p=catagits%2FCatalyst-Runtime.git diff --git a/Changes b/Changes index fbbd97f..3c2d211 100644 --- a/Changes +++ b/Changes @@ -1,6 +1,76 @@ # This file documents the revision history for Perl extension Catalyst. -5.89003 2011-07-XX XX:XX:XX (TRIAL release) +5.9000 - UNRELEASED + + Major changes in this release: + + The Catalyst::Engine classes have all been removed and deprecated, + to be replaced with Plack handlers. + + Plack is an implementation of the PSGI specification, which is + a standard interface between web servers and application frameworks. + + This should be no different for developers, and you should not have to + migrate your applications unless you are using a custom engine already. + + This change benefits Catalyst significantly by reducing the amount of + code inside the framework, and means that the framework gets upstream + bug fixes in Plack, and automatically gains support for any web server + which a PSGI compliant handler is written for. + + It also allows you more flexibility with your application, and allows + the use of cross web framework 'middleware'. + + Developers are recommended to read Catalyst::Upgrading for notes about + upgrading, especially if you are using an unusual deployment method. + + Documentation for how to take advantage of PSGI can be found in + Catalyst::PSGI, and information about deploying your application + has been moved to Catalyst::Manual::Deployment. + + A number of modules have been updated to pass their tests or not + produce deprecation warnings with the latest version of Catalyst. + It is recommended that you upgrade any of these that you are using + after installing this version of Catalyst. + + These extensions are: + + Catalyst::Engine::HTTP::Prefork - this is now deprecated, see + Catalyst::Upgrading. + + Test::WWW::Mechanize::Catalyst - has been updated to not produce + deprecation warnings. + + Catalyst::ActionRole::ACL - has been updated to fix failing tests + (although older versions still function perfectly with this + version of Catalyst). + + Catalyst::Plugin::Session::Store::DBIC - has been updated to fix + failing tests (although older versions still function perfectly + with this version of Catalyst). + + Changelong since the last TRIAL release: + + Backward compatibility fixes: + + - Fix calling MyApp->engine_class to set the engine class manually. + + - Re-add a $res->headers->{status} field to Catalyst::Test responses. + This _should_ be accessed with $c->res->code instead, but is here + for backward compatibility. + + Documentation: + + - Documentation which was in the now removed Catalyst::Engine::* classes + has been moved to Catalyst::Manual::Deployment + + Changes: + + - nginx specific behaviour is removed as it is not needed with any + web server configuration I can come up with (recommended config is + documented in Catalst::Manual::Deployment::nginx::FastCGI) + +5.89003 2011-07-28 20:11:50 (TRIAL release) Backward compatibility fixes: @@ -9,6 +79,9 @@ Bug fixes: + - mod_perl handler fixed to work with application classes which have manually + been made immutable. + - Scripts now force the Plack engine choice manually, rather than relying on auto-detection, as the automatic mechanism gets it wrong if (for example) Coro is loaded. @@ -25,7 +98,10 @@ This fixes compatibility with previous stable releases for applications deployed in these environments. - - Catalyst::Test fixes - XXX FIXME + Enhancements: + + - Catalyst::Test's remote_request method not uses Plack::Test to perform + the remote request. Documentation: - Added a Catalyst::PSGI manual page with information about writing a .psgi @@ -35,7 +111,7 @@ engines clarified. Deprecations: - - Catalyst::Test's local_request function is now deprecate. You should just + - Catalyst::Test's local_request function is now deprecated. You should just use the normal request function against a local server instead. 5.80033 2011-07-24 16:09:00