+Known Bugs:
+
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+ twice when called via ->go or ->visit.
+
+ Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+
+Compatibility warnings to add:
+
+ - $self->config should warn as config should only ever be called as a
+ class method.
+
+Proposed functionality / feature additions:
+
+ - Log setup needs to be less lame, so Catalyst::Plugin::Log::* can die
+ in a fire. Having $c->log_class would be a good start. kane volunteered
+ to do some of this.
+
+ Simple example: Catalyst::Plugin::Log::Colorful should just be a
+ subclass of Catalyst::Log, no ::Plugin:: needed.
+
+ See also: Catalyst::Plugin::Log::Dispatch and
+ http://github.com/willert/catalyst-plugin-log4perl-simple/tree
+
- - Add Class::Accessor compats
- * Catalyst::Request
- * Catalyst::Response
- * Catalyst::Dispatcher
- * Catalyst::Request::Upload
- * Catalyst::Action
- * Catalyst::ActionChain
- * Catalyst::ActionContainer
-
- - Make classes immutable at setup() time
-
-
- - GRODITI's list:
- * Update Test suite to not assume MyApp ISA Controller
- - After that I'll set up attr handlers that will output helpful
- error messages when you do it as well as how to fix it.
- * comments marked /Moose TODO/i in the code
- * Fix the CDI compat hack so we can start moving to immutable
- * Profile before and after immutable.
- * Now would be a good time to lay ground for the App / Ctx split
- * Howto mantain branch in sync with the latest checkins ?
- * Eliminate all instances of $instance->{$key}
- * MooseX::Emulate::CAF seems to be working like a charm :)
- * General code cleanups can't hurt
- * How do we move from NEXT to C3 ? I have never used either of them
- - What does the lineraized mro look like when we are using moose
- method modifiers?
- - Does they all get clumped together or what? Is it a non-issue?