TurboGears Development Status
| Status: | Official |
|---|
The current stable version of TurboGears is 1.0.0.4, which was released on March 8, 2008.
TurboGears 1 Status
TurboGears 1.0 was released on January 3, 2007. The APIs are now stable for all 1.0.x releases. There have been a number of maintenance releases of the 1.0 branch.
The TurboGears 1.0 branch has now entered maintenance mode. This means that all new developments will now occur in the 1.1 branch. The 1.0 branch will only receive critical bug-fixes and security updates from now on.
TurboGears 1.1 Status
Development for version 1.1 takes place in the 1.1 Subversion branch. Documentation for TurboGears 1.1 on the wiki has been started as well.
The TurboGears 1 Team now concentrates on preparing a beta release of the 1.1 branch. The future version 1.1 will provide different defaults for the template engine (Genshi) and the ORM (SQLAlchemy, with Elixer as an option) and should ease transition to the upcoming TurboGears 2.0 for 1.0 users.
For details, please see the 1.1 development plans.
TurboGears 2 Status
The next major version will be TurboGears 2.0 and is under development in the Subversion trunk http://trac.turbogears.org/browser/trunk.
TurboGears 2 will be a (mostly) API compatible reimplementation of the TurboGears platform on top of WSGI, Paste and Pylons. The version in SVN trunk is currently in a working state, with most features from TurboGears 1 ported over. There is a TG2 sprint happening at PyCon in March, and we hope to have a technology preview release soon after that.
TG2 comes with a number of new features:
- A rock solid session system, backed by encrypted cookies, memcached, or a database of your choice.
- Powerful through-the-web debugging tools
- A powerful and flexible Catwalk replacement
- Easy testing via WSGI standard mechanisms (Paste Fixture, or Twill+Scotch)
- Flexible and easy to use Request and Response objects backed by WSGI goodness.
- Improved, more-flexible object dispatch, to make RESTful API's easier
We are not alone here, TG2 is build on top of a lot of great work by Ian Bicking, Ben Bangert, Mike Bayer, Philip Ebby, Philip Jenvy, James Garner, Mike Orr, Chris Percious, Alberto Valverde and many others. Sure, there's a cost to working with others to create and maintain flexible libraries, clean interfaces, and create a working consistent whole out of disparate parts. But we think all the amazing work these folks have done proves that it's worth it.