Thanks for the support Russ... I think Cujo (the name at least) has been abandoned and I have joined my efforts with some other developers also interested in contributing to an experimental branch.
http://github.com/tomxtobin/django-experimental http://groups.google.com/group/django-experimental?hl=en My goal certainly isn't to break backwards compatibility if at all possible. Especially when the first few things I want to take care of... are just tickets I'm cherry picking that have already had significant time and effort invested in them by other django developers. In addition it will definitely help me orient myself with the process of getting patches pushed back upstream. On the other hand, I think it might be a great place for developers to test the waters with features that are a bit more radical...or break backwards compatibility, or are less likely to hit trunk because of scope creep or what-have you. I guess what I'm really looking for is a playground, not really a branch that is necessarily hostile in any way other than the development process will hopefully be a bit more experimental. Hopefully though, much of what happens in django-experimental *eventually*makes it upstream. -k -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
