>> Which brings me to my real question: what is the tg 1 devel team's >> plan for handling abandoned core components (such as cherrpy 2.x)? >> Should these projects be forked and should they start living in >> svn.turbogears.org and be part of tg 1? > > Our plan is to release TG 1.5 very soon, which works with CherryPy 3. It > will also contain some other improvements, e.g. TG widgets will work > with Genshi instead of Kid templates. At the same time, TG 1.5 will stay > as backward compatible as possible. So it will be very easy to upgrade > from TG 1.0/1.1 to TG 1.5, much easier than migrating to TG 2.0. That's > also the primary reason why we want to keep the TG 1.x branch alive. I > think this is the most pragmatic approach to this issue.
Great! I was not totally sure about the future of tg 1.5 but it's good to hear that it's coming. Do you mean that tg widgets will only work with genshi and not kid, or will they work with both? Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown -- 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.
