TG2 beta 2 should come out in the next two days. The only major change should be a simple name-change from tgext.authorization to repoze.what so that the identity like authorization/authentication API can be used in a TG2 independent manner by other WSGI applications. After Beta 2 I expect RC1 to come out within a bit over a week. RC1 could turn into 1.9.7 final, which would be an API stable, supported version of TG2. There will likely be some API changes between 1.9.7 and 2.0, but we will try to keep them to a minimum, and will document upgrade procedures thoroughly.
As for your second question, repoze.workflow seems like an interesting workflow implementation that could be used in a tg2 app. It's a relatively new project, but is also pretty well contained and seems like it's well thought out. http://svn.repoze.org/repoze.workflow/trunk/ On Wed, Nov 5, 2008 at 4:35 PM, Grzegorz Staniak <[EMAIL PROTECTED]> wrote: > > Hi, > > In a week or two I'm starting a medium-size project using TG. Does it > make sense to choose TG2 at this moment? I gather TG2 is approaching > beta status, can I assume a frozen feature-set and stable interfaces? > > Also, the project involves a workflow implementation - are you aware of > TG apps (or generally Python apps), libs, engines that could be used > as a base for a workflow app? > > GS > -- > Grzegorz Staniak <gstaniak _at_ gmail [dot] com> > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
