I'm glad this is finally out. I'll like to thank everyone for the hard work put here !
On Fri, Nov 19, 2010 at 6:28 PM, Chris Perkins <ch...@percious.com> wrote: > The TurboGears team is proud to present TurboGears 2.1. 2.1 has been in > development for about one year with the first alpha released in October of > 2009. If you haven’t been following along, here is a review of the changes > that 2.1 brings from 2.0. > > Better performance. The TG team worked hard profiling to see what could be > done to make TG faster. 2.1 is at least 20% faster than 2.0 on page-loads > as a result. > Better Mako support. (quickstart template now includes a --mako option) If > you want a highly performant website, Mako is a better option than genshi. > Kajiki support. This template engine is for those who like the XML > templating on Genshi, but need much better performance. > Re-written dispatcher. Object Dispatch has now become Abstract Dispatch, > and the code that decides which controller method should be executed has > been refactored and consolidated. An open API is provided for those that > want to create their own dispatch mechanisms by using the _dispatch method > in your controllers. > Pylons 1.0 support. Those of you still running 0.9.7 can do so as well. TG > 2.1 is cross -compatible, which means if you have a 2.0 application, you > needn’t upgrade to Pylons 1.0 until you decide to. > Reduced dependencies. For those of you who use TG as a service, or do not > need database or an admin, TG has reduced it’s dependencies to the low-20s. > The full stack with SQLAlchemy and an admin still has more packages, but the > packages which were most difficult to install have been removed (those > requiring RuleDispatch in particular). > Finally, documentation improvements. The documentation has been visually > overhauled, reorganized, and brought up to date. There is still > considerable work to do in this area, but a significant effort has been made > to solidify those areas which are most often asked about by our users. > > TurboGears is committed to maintaining the 2.x branch for the long-term. > This release is intended not to make significant strides in capability, > rather to refine our existing functionality in order to add significant > consistency to the codebase. We have already started working on a 2.2 > branch, which continues this effort, and will open up more APIs to the > framework. We look forward to your continued support! > > A special thanks goes out to all of you who made this release possible. > Without the dedication from folks writing docs, providing feedback and > bugfixes, this release could not have happened. We look forward to the > continued community support for the future to come. > > cheers. > > -chris > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-tr...@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
