>>> So, to wrap it up: I won't and can't speak out against this move - you >> guys do, what you do. It's a technically sound decision. > > Most of all I think it's *organizationally* sound. > > Of course, we should also discuss how we can make sure existing TG1 and TG2 > projects can be migrated to Pyramid or happily continue to run with TG1 or > TG2 for many years. I'm all for finishing TG 2.1 (properly, not in a hurry) > and providing bugfix releases in the future. I'll also continue to provide > bugfix releases for TG 1.1 and there will be a TG 1.5 alpha release soon for > people who want to stick with CherryPy.
So, I think we *absolutely must* make sure we continue to support the current code that's out there both 2.x and 1.x. And I think we need to make it super trivial to make your existing 1.x or 2.x application a part of a pyramid project without any modification whatsoever, so that migrations can be done in a controlled and sane way as real requirements come in that make the migration work worth doing. --Mark Ramm -- You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en.
