The next major release of TurboGears is not going to be called 1.1 after all. I think 2.0 will be a much more appropriate number.
I've already talked about what the idea is with this new version. I'll reiterate it here and add one more minorish/majorish item: 1) CherryPy 3.0 - faster, cleaner, more extensible. What's not to like? 2) SQLAlchemy - once you switch, you'll never go back 3) Genshi - a solid upgrade from Kid 4) Multiple applications (WSGI and TG) - CherryPy 3 implements some of the goodies that we need for neatly composing web sites from multiple applications. Genshi's XInclude syntax largely fixes the problems that we had with providing site-wide styling. 5) Simplified decorators - the decorators change from being true decorators to registering behavior that will be applied. I believe that this will make our code dramatically simpler. (BTW, "quicker startup" isn't on this list, because I think we'll address this in a 1.0x release, given that we know what the problem is). The new item for the list is: 6) Break out more of our code #6 is very important. After 0.8, TurboGears grew quite a bit of code and features for 0.9. It made sense at the time to put them all in the turbogears package, because the whole point of those features was to build on services that TG provides. However, I think there's really much greater value to us and the Python community as a whole if we make *as much functionality as possible* available as separate pieces with the minimum required dependencies to do their jobs well. It'll make it easier to experiment with new features in certain areas, too. Though ToscaWidgets is a rewrite, the idea is the same: pieces of TurboGears will break out into separate projects (ideally each with their own maintainer) that can grow and evolve more quickly. These projects can live in the TG repository in /projects with their own tags/branches/trunk so they can evolve and release as needed. If you're interested in taking on a piece of TG, let me know. When you look at the list above, you can see that TurboGears 2.0 is indeed a major and important upgrade for TurboGears. The interesting bit is that that actual amount of work involved is not that large. I'd actually start in on it tomorrow, if it weren't for the small matter that 1.0 needs a bit of finishing :) 2.0 will be released closer to 1.0's release than might be common, but TurboGears 1.0 has truly been seeing significant use since the first alpha release just before PyCon in February. To reiterate: I'm looking for people to take control of things like i18n, Catwalk, FastData, Identity, etc. (BTW, we do need to figure out what to do with Identity in general, since we have an alternative model that's been put forth...) Kevin -- Kevin Dangoor TurboGears / Zesty News email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
