list the authordeps in a cpanfile for easier installation

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index af08355..999e237 100644 (file)
--- a/TODO
+++ b/TODO
@@ -24,61 +24,17 @@ subclass of Catalyst::Log, no ::Plugin:: needed.
 See also: Catalyst::Plugin::Log::Dispatch and
 http://github.com/willert/catalyst-plugin-log4perl-simple/tree
 
-# REFACTORING
+## throw away the restarter and allow using the restarters Plack provides
 
-##  PSGI
-
-###  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?
-
-  * 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.
-
-  * Where do all the setup docs from Engine::* go? Into the Manual?
-    At least for nginx, these are somewhat cat specific
-
-  * 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
+## be smarter about how we use PSGI - not every response needs to be delayed
     and streaming
 
-##  The horrible hack for plugin setup - replacing it:
+#  The horrible hack for plugin setup - replacing it:
 
  * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
    I wonder if what we need is that combined with plugins-as-roles
 
-## App / ctx split:
+# App / ctx split:
 
   NOTE - these are notes that t0m thought up after doing back compat for
          catalyst_component_class, may be inaccurate, wrong or missing things