X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=694dc0e0bbd7ebea307b3ee83a31eb13b7d7e86e;hb=d91474f509dab7dce4c3e4328e674ab9fea29284;hp=7a0c0039c6d63bea79fa822854bc2797ea799b69;hpb=730533aeeda86c4934c6fdf0bb714366fa8bddc2;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index 7a0c003..694dc0e 100644 --- a/TODO +++ b/TODO @@ -1,10 +1,15 @@ Pending patches: - meta test for MX::Emulate::CAF needed by Catalyst::Plugin::Cache::Curried + + - Class::Accessor::Chained::Fast test for MX::Emulate::CAF, to fix + HTML::Widget + + - Re-opening packages with MX::Emulate::CAF (for + Catalyst::Plugin::HashedCookies) + +Back-compat investigation / known issues: - - Adopt::NEXT - - updated docs with how to disable it (t0m/rafl) - -Back-compat investigation / konwon issues: + - FIXME notes in Catalyst::Dispatcher - Common engine test failures, look into and get tests into core. @@ -14,12 +19,40 @@ Back-compat investigation / konwon issues: - Run another round of repository smokes against latest 5.80 trunk, manually go through all the things which are broken (t0m). + + - Catalyst::Plugin::Authorization::ACL + - Catalyst::Plugin::Server + - Should hopefully be fixed now.. + + - Catalyst-Plugin-Cache dies due to mk_accessors('meta') + + - Catalyst-Action-REST appears to have real issues, investigate + + - Catalyst-Model-Search ditto + + - CatalystX-CRUD ditto + + - Catalyst-Engine-Apache - Deep recursion on subroutine + "Catalyst::Action::execute", investigate once all other tests pass + + - Catalyst-Plugin-Scheduler + - Catalyst-Engine-HTTPEngine + - Catalyst-View-HTML-Template + - Catalyst-View-XSLT + - Catalyst-Plugin-Setenv + - Catalyst-Plugin-RequireSSL - Bullshit 'cannot locate' errors + Bug in smoke test rig. - Issues with TWMC not being loaded when it used to be in 5.70 (Bill Moseley) - Fix memory leaks (I already tried Devel::Leak::Object, but no joy). + - In 5.70, you can have a component which doesn't inherit from ::Component, + and has no new method, and it'll do the right thing for you. We just + ignore that, we should still support that, but warn for/deprecate it so + it can go for 5.9X... + This all obviously needs better tests :/ Cleanups: