<?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.1 and Beyond</title>
	<atom:link href="http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/feed/" rel="self" type="application/rss+xml" />
	<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/</link>
	<description>Thinking about programming in new ways</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:00:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Mark Ramm</title>
		<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-73967</link>
		<dc:creator>Mark Ramm</dc:creator>
		<pubDate>Wed, 04 Jul 2007 22:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-73967</guid>
		<description>Dieter, 

Thanks for the feedback.   I understand what you are saying -- and I have to say I agree with the sentement, but not the strategy. 

We need to do a bit more work on TurboGears 2 in order to get it to the point where it is easy to use and easy to upgrade too, so stopping development now would be a mistake. 

But I fully intend to create a document &quot;Upgrading the 20 min Wiki&quot; which takes the 20 min wiki and moves it to TurboGears 2.   I think you&#039;ll find that it&#039;s really easy -- which is a requirement for me personally because I have some large TurboGears projects which I&#039;ll need to migrate to TG2.  

So, I personally am very committed to making it easy to upgrade, because if it isn&#039;t I&#039;ll be hurting myself. ;)</description>
		<content:encoded><![CDATA[<p>Dieter, </p>
<p>Thanks for the feedback.   I understand what you are saying &#8212; and I have to say I agree with the sentement, but not the strategy. </p>
<p>We need to do a bit more work on TurboGears 2 in order to get it to the point where it is easy to use and easy to upgrade too, so stopping development now would be a mistake. </p>
<p>But I fully intend to create a document &#8220;Upgrading the 20 min Wiki&#8221; which takes the 20 min wiki and moves it to TurboGears 2.   I think you&#8217;ll find that it&#8217;s really easy &#8212; which is a requirement for me personally because I have some large TurboGears projects which I&#8217;ll need to migrate to TG2.  </p>
<p>So, I personally am very committed to making it easy to upgrade, because if it isn&#8217;t I&#8217;ll be hurting myself. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dieter</title>
		<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-73913</link>
		<dc:creator>Dieter</dc:creator>
		<pubDate>Wed, 04 Jul 2007 20:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-73913</guid>
		<description>So, why should I use TurboGears at all after its developers throw away half of its components to replace them with others which will be more or less compatible? My suggestion to you TG core developers is: Stop developing TG2 now, at least for a little moment, and show your users how they will migrate their TG1 projects to TG2. If you don&#039;t make that point clear how the upgrade path is and that that path is very easy to go then you will really loose a lot of your users to other frameworks.</description>
		<content:encoded><![CDATA[<p>So, why should I use TurboGears at all after its developers throw away half of its components to replace them with others which will be more or less compatible? My suggestion to you TG core developers is: Stop developing TG2 now, at least for a little moment, and show your users how they will migrate their TG1 projects to TG2. If you don&#8217;t make that point clear how the upgrade path is and that that path is very easy to go then you will really loose a lot of your users to other frameworks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-71180</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 28 Jun 2007 18:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-71180</guid>
		<description>&lt;strong&gt;Web-Frameworks: TurboGears 2.0 wird auf Pylons aufsetzen...&lt;/strong&gt;

Wer vor der Frage steht, ob er TurboGears oder Pylons nutzen will, bekommt bald eine interessante Antwort: Beides gleichzeitig....</description>
		<content:encoded><![CDATA[<p><strong>Web-Frameworks: TurboGears 2.0 wird auf Pylons aufsetzen&#8230;</strong></p>
<p>Wer vor der Frage steht, ob er TurboGears oder Pylons nutzen will, bekommt bald eine interessante Antwort: Beides gleichzeitig&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Gardner &#187; Pylons and TurboGears 2.0</title>
		<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-71083</link>
		<dc:creator>James Gardner &#187; Pylons and TurboGears 2.0</dc:creator>
		<pubDate>Thu, 28 Jun 2007 12:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-71083</guid>
		<description>[...] TurboGears&#8217; announcement that version 2.0 will be built on Pylons. If this is news to you see Mark Ramm, and Jonathan LaCour&#8217;s posts and the mailing list thread. It is great to see such positive [...]</description>
		<content:encoded><![CDATA[<p>[...] TurboGears&#8217; announcement that version 2.0 will be built on Pylons. If this is news to you see Mark Ramm, and Jonathan LaCour&#8217;s posts and the mailing list thread. It is great to see such positive [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NotÃ­cias recentes sobre o TurboGears &#171; Mosaico Livre</title>
		<link>http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-70935</link>
		<dc:creator>NotÃ­cias recentes sobre o TurboGears &#171; Mosaico Livre</dc:creator>
		<pubDate>Thu, 28 Jun 2007 03:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2007/06/27/turbogears-11-and-beyond/#comment-70935</guid>
		<description>[...] hoje apareceram dois posts importantes, pois tratam do futuro do framework. O primeiro que li foi o post do Mark Ramm, resumindo os acontecimentos e decisÃµes tomadas num sprint [...]</description>
		<content:encoded><![CDATA[<p>[...] hoje apareceram dois posts importantes, pois tratam do futuro do framework. O primeiro que li foi o post do Mark Ramm, resumindo os acontecimentos e decisÃµes tomadas num sprint [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
