> How will this migration to TG 2.0 with Pylon affect existing user > projects that currently use the current 1.x TG code base? Most > importantly for my team, what are the TG teams plans for legacy code > compatibility and clearly defined migration paths if required?
There will be a clearly defined migration path from 1.x to 2.0, and 1.x versions will be actively maintained after 2.0 is out for a significant amount of time so you'll be able to migrate on whatever schedule is right for your project. Since we're using a new package name, we even have the option of keeping the 1.x line around and supported for a very, very, very long time. As for migration paths, even though we will switch default model and template engine to SQLAlchemy and Genshi, Kid and SQLObject will be supported in 2.0. So, unless you are doing some trickery, you will be able to copy over you models wholesale, and many of templates should also be trivial to migrate. The only places you'll have to do migration will be in your controller code, and possibly your tests. Before we release 2.0 there will be a clearly documented list of changes, and a migration checklist. --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 -~----------~----~----~----~------~----~------~--~---
