> Frankly speaking I'm afraid a little. It seems to me that turbogears > guys are going to break everything in the next milestone and make a > completely new framework. Though they will try to leave the same API > as in 1.0 it will relatevely be broken and the code style will change. > So it will be hard to improve and support my project if further > framework developement will go on in the same manner.
There will be changes between TG 1 and TG 2 that's true. But I don't think they will be as as major as you think, and I don't think "relatively broken" is a good characterization of what we're doing. We are improving a few API's that weren't what we wanted in the first place, and we're making a couple of small changes to be more Pylons friendly. But I've done a couple of test ports of 1.x code to 2.0 , and they have been very quick and required very few code changes. I also agree with what other people have been saying -- we are making a big push to get TG2 to the place where it will be stable for a very long time. The components in TG2 from SQLALchemy to Pylons and Genshi all have active developer communities and are going to be very viable long term. We are planning for the future this time thinking about long term viability, planning for extensibility, breaking out components into smaller projects with dedicated teams, and otherwise doing everything in our power to make sure that what we release this time will be viable for a long time. It's is valid to say that tg1 was very much a framework designed on the best stuff available "at the moment" when Kevin needed them for a project. This resulted in a remarkably useful framework. But not a lot of thought went into making the framework future proof. We've even had major components with absent maintainers. Fortunately the size of theTurboGears community, and the quality of our users has meant that users have stepped up to take over maintenance of subprojects (Kid is the best example) which were somewhat abandoned by their original creators. I think if you look at other next-gen web frameworks (Rails, Pylons, Django, etc) TurboGears 1.x already has one of the longest stable support lifetimes, and we plan to continue that out long enough that I have no doubt that we will absolutely have the longest support schedule around. And I think you'll find that even major TurboGears projects will be relatively easy to port to TG2, which will be supported for even longer. --Mark Ramm TG2 Maintainer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
