<?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: Deployment is the goal</title> <atom:link href="http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/feed/" rel="self" type="application/rss+xml" /><link>http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/</link> <description>Continuous Integration, Delivery and Devops Consulting</description> <lastBuildDate>Thu, 02 Feb 2012 22:31:14 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: simpsonjulian</title><link>http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/comment-page-1/#comment-401</link> <dc:creator>simpsonjulian</dc:creator> <pubDate>Sun, 06 Sep 2009 22:02:53 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/08/17/deployment-is-the-goal#comment-401</guid> <description>Gary, thanks for the comment.  I wouldn&#039;t shoot you down.  The moment a dev team thinks that testing is someone else&#039;s problem, the rot sets in.  Or the build, for that matter.</description> <content:encoded><![CDATA[<p>Gary, thanks for the comment.  I wouldn&#8217;t shoot you down.  The moment a dev team thinks that testing is someone else&#8217;s problem, the rot sets in.  Or the build, for that matter.</p> ]]></content:encoded> </item> <item><title>By: Gary</title><link>http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/comment-page-1/#comment-402</link> <dc:creator>Gary</dc:creator> <pubDate>Sun, 06 Sep 2009 02:28:29 +0000</pubDate> <guid
isPermaLink="false">http://www.build-doctor.com/2009/08/17/deployment-is-the-goal#comment-402</guid> <description>Nice piece. There&#039;s a reason why companies, and even volunteer projects, don&#039;t instinctively want to release very frequently: experience teaches us that releases introduce bugs. The key to overcoming this resistance to frequent releases is (IMHO) comprehensive functional and non-functional testing. As all the non-developer types involved with a release gain confidence in the release process as solid, so the frequency of releases can be accelerated.
I&#039;m not a developer, so it&#039;s easy for me to say, but the better the dev team I&#039;ve worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down....</description> <content:encoded><![CDATA[<p>Nice piece. There&#8217;s a reason why companies, and even volunteer projects, don&#8217;t instinctively want to release very frequently: experience teaches us that releases introduce bugs. The key to overcoming this resistance to frequent releases is (IMHO) comprehensive functional and non-functional testing. As all the non-developer types involved with a release gain confidence in the release process as solid, so the frequency of releases can be accelerated.</p><p>I&#8217;m not a developer, so it&#8217;s easy for me to say, but the better the dev team I&#8217;ve worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down&#8230;.</p> ]]></content:encoded> </item> </channel> </rss>
