<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: What exactly is Build/Release</title>
	<atom:link href="http://code-bear.com/bearlog/2010/01/29/what-exactly-is-buildrelease/feed/" rel="self" type="application/rss+xml" />
	<link>http://code-bear.com/bearlog/2010/01/29/what-exactly-is-buildrelease/</link>
	<description>Gravity is the root of lightness; stillness, the ruler of movement</description>
	<lastBuildDate>Sat, 10 Jul 2010 14:17:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Fritzy</title>
		<link>http://code-bear.com/bearlog/2010/01/29/what-exactly-is-buildrelease/comment-page-1/#comment-164</link>
		<dc:creator>Fritzy</dc:creator>
		<pubDate>Fri, 29 Jan 2010 13:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://code-bear.com/bearlog/2010/01/29/what-exactly-is-buildrelease/#comment-164</guid>
		<description>Reading this brings out some flaws in my own processes -- in particular pointing users to the issue tracker in the README and clearly definable versions come to mind, though I have gotten better about this.&lt;br&gt;&lt;br&gt;When you start talking about a clean install on a machine that is not your dev environment, the words &quot;continuous integration&quot; come to mind.  If you can automate some QA, then that&#039;s better than nothing, and having something automatically check out new builds and install them fresh somewhere other than your dev environment, that can catch a lot of bugs.  &quot;Works on my machine&quot; is not a valid response to a bug by a developer.  What if you forgot to add a file to a repo (something I do on occasion) -- testing it on your box expose the problem that your users will face.&lt;br&gt;&lt;br&gt;Ralph Meijer recently pointed me to buildbot for continuous integration and I may try it out.</description>
		<content:encoded><![CDATA[<p>Reading this brings out some flaws in my own processes &#8212; in particular pointing users to the issue tracker in the README and clearly definable versions come to mind, though I have gotten better about this.</p>
<p>When you start talking about a clean install on a machine that is not your dev environment, the words &#8220;continuous integration&#8221; come to mind.  If you can automate some QA, then that&#39;s better than nothing, and having something automatically check out new builds and install them fresh somewhere other than your dev environment, that can catch a lot of bugs.  &#8220;Works on my machine&#8221; is not a valid response to a bug by a developer.  What if you forgot to add a file to a repo (something I do on occasion) &#8212; testing it on your box expose the problem that your users will face.</p>
<p>Ralph Meijer recently pointed me to buildbot for continuous integration and I may try it out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
