<?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: Why Drizzle Will Succeed</title>
	<atom:link href="http://www.pythian.com/news/1183/why-drizzle-will-succeed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/1183/why-drizzle-will-succeed/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Jay Pipes</title>
		<link>http://www.pythian.com/news/1183/why-drizzle-will-succeed/#comment-265183</link>
		<dc:creator>Jay Pipes</dc:creator>
		<pubDate>Tue, 26 Aug 2008 16:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1183/why-drizzle-will-succeed#comment-265183</guid>
		<description>Hehe, as one of the ones with commit access, I couldn&#039;t agree with you and Brian more.  The *only* times I have committed to trunk is to merge other people&#039;s code after merging and build/testing locally.  Commits to trunk should only be that: merges from developer branches (Brian? ;) ).  It *is* drudgery work, but it&#039;s absolutely necessary to keep commits to trunk to a minimum.  Development happens in branches outside of trunk and trunk is merely the merging of development outside trunk into trunk once a branches&#039; code tests and builds cleanly...

-jay</description>
		<content:encoded><![CDATA[<p>Hehe, as one of the ones with commit access, I couldn&#8217;t agree with you and Brian more.  The *only* times I have committed to trunk is to merge other people&#8217;s code after merging and build/testing locally.  Commits to trunk should only be that: merges from developer branches (Brian? ;) ).  It *is* drudgery work, but it&#8217;s absolutely necessary to keep commits to trunk to a minimum.  Development happens in branches outside of trunk and trunk is merely the merging of development outside trunk into trunk once a branches&#8217; code tests and builds cleanly&#8230;</p>
<p>-jay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Seiler</title>
		<link>http://www.pythian.com/news/1183/why-drizzle-will-succeed/#comment-264642</link>
		<dc:creator>Don Seiler</dc:creator>
		<pubDate>Mon, 25 Aug 2008 22:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1183/why-drizzle-will-succeed#comment-264642</guid>
		<description>I wholeheartedly agree re commit access.  As a former maintainer for Gentoo Linux, I had commit access to the entire portage tree.  Sure, there was a sense of elite power, but that lasted all of maybe 1 week.  Once you start having to deal with upstream changes and user-submitted patches and maintaining stable vs unstable versions, it becomes a chore.  You quickly become the servant more than the master of the project.

At least, that is how I saw my role progressing.</description>
		<content:encoded><![CDATA[<p>I wholeheartedly agree re commit access.  As a former maintainer for Gentoo Linux, I had commit access to the entire portage tree.  Sure, there was a sense of elite power, but that lasted all of maybe 1 week.  Once you start having to deal with upstream changes and user-submitted patches and maintaining stable vs unstable versions, it becomes a chore.  You quickly become the servant more than the master of the project.</p>
<p>At least, that is how I saw my role progressing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

