Hi, There is a page about development status here:
http://www.turbogears.org/about/status.html As far as I've seen, there's only been one backwards incompatible change so far, and that's documented in the changelog: http://www.turbogears.org/svn/turbogears/trunk/CHANGELOG.txt My plan as of now is to have a 0.8 release (formerly 0.6) this week. 0.9 will be released sometime after the sprint on the 8th. After that, there will be 1.0 beta and 1.0 final will be considered to have a stable API. What I could do is add an "a" to 0.8 and 0.9 just to make it clear that those releases are considered to have possibly unstable APIs. Kevin On 10/3/05, Lethalman <[EMAIL PROTECTED]> wrote: > > (sorry for my poor English) > > Everyone knows turbogears isn't a stable product yet because it's at > the beginning and its changes are in the core of the program. > So i'm thinking that an user who wants to make his own web application > and get a look for turbogears, he sees that it's stable and launched > because the turbogears version is not a beta or an alpha... then when > releasing the next version the user needs to do a refactoring and i > think it's not good. > Pheraps i suggest to make beta versions of turbogears before releasing > a very stable and non-dynamic core the product. > > Hope you understand my text :P > > -- > www.italianpug.org - Italian Python User Group Founder > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
