Catalyst::Upgrading - Instructions for upgrading to the latest Catalyst
-=head2 Upgrading to Catalyst 5.90
+=head1 Upgrading to Catalyst 5.90
The major change is that L<Plack> now replaces most of the subclasses of
L<Catalyst::Engine>. If you are using one of the standard subclasses of
Advice for specific subclasses of L<Catalyst::Engine> follows:
-=head3 Upgrading the FastCGI Engine
+=head2 Upgrading the FastCGI Engine
No upgrade needed if your myapp_fastcgi.pl script is already upgraded
enough to use L<Catalyst::Script::FastCGI>.
-=head3 Upgrading the mod_perl / Apache Engines
+=head2 Upgrading the mod_perl / Apache Engines
The engines that are build upon the various iterations of mod_perl,
L<Catalyst::Engine::Apache::MP13> and
L<Catalyst::Engine::Apache2::MP19>, is however no longer supported, as Plack
does not support mod_perl version 1.99??? FIXME - is this true?
-=head3 Upgrading the HTTP Engine
+=head2 Upgrading the HTTP Engine
The default development server that comes with the L<Catalyst> distribution
should continue to work as expected with no changes as long as your C<myapp_server>
script is upgraded to use L<Catalyst::Script::HTTP>.
-=head3 Upgrading the CGI Engine
+=head2 Upgrading the CGI Engine
If you were using L<Catalyst::Engine::CGI> you should now use...
No upgrade needed if your myapp_cgi.pl script is already upgraded
enough to use L<Catalyst::Script::CGI>.
-=head3 Upgrading the Preforking Engine
+=head2 Upgrading the Preforking Engine
If you were using L<Catalyst::Engine::HTTP::Prefork> then L<Starman>
is automatically loaded.
-=head3 Upgrading the PSGI Engine
+=head2 Upgrading the PSGI Engine
If you were using L<Catalyst::Engine::PSGI> this new release supercedes this
engine in supporting L<Plack>. You should remove the.. FIXME