<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: TurboGears 1.0.6 released</title>
	<atom:link href="http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/</link>
	<description>Thinking about programming in new ways</description>
	<lastBuildDate>Tue, 15 Mar 2011 02:30:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Florent Aide</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-231010</link>
		<dc:creator>Florent Aide</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:57:03 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-231010</guid>
		<description>Andy: 1.0.6 is really just that: a maintenance release to further stabilize the 1.0.x branch. Read the full changelog and decide if it is interesting to upgrade for your applications.

If none of the fixes are interesting to your use case you can definitely wait for the 1.1 release. The 1.1 release on the opposite will really be a &quot;must upgrade&quot; release.</description>
		<content:encoded><![CDATA[<p>Andy: 1.0.6 is really just that: a maintenance release to further stabilize the 1.0.x branch. Read the full changelog and decide if it is interesting to upgrade for your applications.</p>
<p>If none of the fixes are interesting to your use case you can definitely wait for the 1.1 release. The 1.1 release on the opposite will really be a &#8220;must upgrade&#8221; release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Florent Aide</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-231009</link>
		<dc:creator>Florent Aide</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-231009</guid>
		<description>Graham: Yes you&#039;re right. But we&#039;re mostly working with mod_wsgi in head. That&#039;s why I put it that way.</description>
		<content:encoded><![CDATA[<p>Graham: Yes you&#8217;re right. But we&#8217;re mostly working with mod_wsgi in head. That&#8217;s why I put it that way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Ramm</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-231007</link>
		<dc:creator>Mark Ramm</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-231007</guid>
		<description>Andy, 

Here&#039;s the changelog: 

http://trac.turbogears.org/wiki/ChangeLog#a1.0.6August262008:

But there aren&#039;t many new features in 1.0.6, just small tweeks, and a half dozen or so bugfixes.</description>
		<content:encoded><![CDATA[<p>Andy, </p>
<p>Here&#8217;s the changelog: </p>
<p><a href="http://trac.turbogears.org/wiki/ChangeLog#a1.0.6August262008" rel="nofollow">http://trac.turbogears.org/wiki/ChangeLog#a1.0.6August262008</a>:</p>
<p>But there aren&#8217;t many new features in 1.0.6, just small tweeks, and a half dozen or so bugfixes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Ramm</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-231006</link>
		<dc:creator>Mark Ramm</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:46:52 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-231006</guid>
		<description>Graham,

Agreed it&#039;s pretty much just a fix for TurboGears WSGI support.   I think that Florent can be excused for putting it that way because mod_wsgi is the most common wsgi server that people want to use with non-root mount points for their turbogears apps.  ;)</description>
		<content:encoded><![CDATA[<p>Graham,</p>
<p>Agreed it&#8217;s pretty much just a fix for TurboGears WSGI support.   I think that Florent can be excused for putting it that way because mod_wsgi is the most common wsgi server that people want to use with non-root mount points for their turbogears apps.  ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Dumpleton</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-230874</link>
		<dc:creator>Graham Dumpleton</dc:creator>
		<pubDate>Thu, 28 Aug 2008 00:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-230874</guid>
		<description>What you call &#039;enhanced mod_wsgi compatibility&#039; actually isn&#039;t and those changes would apply to any WSGI hosting mechanism. :-)</description>
		<content:encoded><![CDATA[<p>What you call &#8216;enhanced mod_wsgi compatibility&#8217; actually isn&#8217;t and those changes would apply to any WSGI hosting mechanism. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy grover</title>
		<link>http://compoundthinking.com/blog/index.php/2008/08/27/turbogears-106-released/#comment-230859</link>
		<dc:creator>andy grover</dc:creator>
		<pubDate>Wed, 27 Aug 2008 23:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/?p=371#comment-230859</guid>
		<description>can&#039;t wait for that improved wsgi -- I know there are ways to do it now but the trouble has kept me running tg in a screen instance and using apache http_proxy. Pretty lame.

BTW I found it a little funny you listed all the upcoming 1.1 features (i.e. not yet available) in this post, which I would have guessed from the title would have been mostly about 1.0.6. So what about 1.0.6, worth upgrading?</description>
		<content:encoded><![CDATA[<p>can&#8217;t wait for that improved wsgi &#8212; I know there are ways to do it now but the trouble has kept me running tg in a screen instance and using apache http_proxy. Pretty lame.</p>
<p>BTW I found it a little funny you listed all the upcoming 1.1 features (i.e. not yet available) in this post, which I would have guessed from the title would have been mostly about 1.0.6. So what about 1.0.6, worth upgrading?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

