X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=TODO;h=6d64457ac4cc24930c96bcf342ff4427448eb909;hp=b9e890bd56224b89478d76854e503a93401af029;hb=b9f72120e78ad2b0bb2e2fe8dee3732b4496b99c;hpb=c0820fbe8e74d41ab3533d0742f7158b8c7a8404

diff --git a/TODO b/TODO
index b9e890b..6d64457 100644
--- a/TODO
+++ b/TODO
@@ -28,31 +28,50 @@ http://github.com/willert/catalyst-plugin-log4perl-simple/tree
 
 ##  PSGI
 
+###  To do at release time
+
+  - Release psgi branch of Catalyst-Devel
+  - Release new Task::Catalyst
+  - Release 5.9 branch of Catalyst-Manual
+
 ###  Blockers
 
-  * Add some tests for Catalyst::Test::local_request
-  * Test all the options work on all of the scripts
-  * Test (and fix if needed) ::Wx
-  * Document how to use your own .psgi (and how you need to do ReverseProxy yourself if you do)
-  * Document migration for setting engine in setup
-  * Document migration for setting engine in $ENV
-  * Fix Catalyst::Engine::PSGI .psgi script and in app root running tests.
+  * 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.
+
+  * Finish fixing up Catalyst::Manual::Deployment and update for psgi.
+
+  * 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
 
-  * Do we need to do something else about middleware than let the user provide a .psgi?
-    What about the reverse proxy middleware
-  * Do we generate a .psgi by default?
-  * throw out Catalyst::Test's remote_request in favour of
-    Plack::Test::ExternalServer
-  * 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
+  * 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
-  * lighttpd, iis6, and nginx path-info fixers as proper middlewars as part of Plack
 
 ##  The horrible hack for plugin setup - replacing it: