There has been lots of great work done on the 2.1 code in hg.turbogears.org, chris has rewritten the dispatcher, Jorge has a new much slimmer TurboJson alternative for automatic jsonification, and there's quite a few other performance enhancements.
There was talk about a new YAML based config system, new quickstart template code, pylons trunk (1.0) code support, explicit support for site--components, etc. I'd like these things to be done as soon as possible, but I think releasing a 2.1 alpha with what we have now would be valuable. And I think we should keep a clean trunk so that we can release 2.1 whenever the time is right. So, I think that all "potentially disruptive" work should be done in hg branches and then merged back to the "trunk" as the projects are completed. I also think we should try to get a 2.1 alpha ready by somewhere between the 5th and 12th of June. This will give 2.0 some time to settle down into people's bones, but will also get a 2.1a1 out before the summer doldrums sets in. And it would be great to get lots of the shiny goodness that's in 2.1 already out into people's hands to try out. Ultimately I think it's better to release the work that's done now sooner rather than later, and to continue to have more and smaller releases. So if the new features are not ready, in time for 2.1 they will be ready for 2.2 ;) -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
