## PSGI
+### To do at release time
+
+ - Release psgi branch of Catalyst-Devel
+ - Release new Task::Catalyst
+ - Release 5.9 branch of Catalyst-Manual
+
### Blockers
- * Test all the options work on all of the scripts
- * Fix nginx middlewares so that they are generic, or can somehow
- be used by people with their own .psgi files
- * Fix a sane / nicer way to do custom engines.
+ * Test::WWW::Mechanize::Catalyst new release
+
+ * Test everything in the %conflicts list
+
+ * Test tutorial apps
+
+ * Test nginx middleware to determine if it is needed with:
+
+ root app - with use_request_uri_for_path
+ root app - without use_request_uri_for_path
+ non-root app - with use_request_uri_for_path
+ non-root app - without use_request_uri_for_path
+
+ If it isn't needed, remove. If it is needed, split it out into it's own
+ file and document why it's needed.
+
+ * I've noticed a small difference with Catalyst::Test. The latest stable
+ version include two headers, 'host' and 'https'. They are missing from
+ this version - Pedro Melo on list
+ ^^ Cannot replicate this? Mailed back to ask for tests..
### Nice to have
- * <@rafl> i've been thinking of maybe providing
- MyApp->apply_default_middlewares($psgi_app)
+ * Test/WWW/Mechanize/Catalyst.pm stable throws a deprecation alert when
+ using Catalyst::Test changes introduced by Cataplack. Suggested fix is
+ in the repo: http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=14059
+
* Capture arguments that the plack engine component was run with somewhere,
- to more easily support custom args from scripts (e.g. Gitalist's
+ to more easily support custom args from scripts (e.g. Gitalist's
--git_dir)
* throw away the restarter and allow using the restarters Plack provides
* remove per-request state from the engine instance