## PSGI
- * throw out Catalyst::Test's remote_request in favour of
- Plack::Test::ExternalServer
- * Fix Test::WWW::Mechanize::Catalyst which has been broken by moving stuff
- about.
- * properly pass along server arguments
- * move disabled tests in unit_core_engine_cgi-prepare_path.t into Plack
- * think about whether or not to generate myapp.psgi and how to configure
- middleware
- * make sure we're running under a server that support psgi.streaming - maybe
- just load the BufferedWrite middleware, although that might break things
- relying on ->write doing an unbuffered write
+### To do at release time
+
+ - Release psgi branch of Catalyst-Devel
+ - Release new Task::Catalyst
+
+### Blockers
+
+ * Test everything in the %conflicts list
+
+ * Anything left in Task::Catalyst failing?
+
+ * Test tutotial apps?
+
+ * Fix nginx middlewares so that they are generic, or can somehow
+ be used by people with their own .psgi files
+
+ * 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
+
+ * 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
+ --git_dir)
* throw away the restarter and allow using the restarters Plack provides
* remove per-request state from the engine instance
* be smarter about how we use PSGI - not every response needs to be delayed
and streaming
- * figure out how to not break existing mod_perl deployments
## The horrible hack for plugin setup - replacing it: