Comments on: Deployment is the goal http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/ Helping to deliver working software, one continuous integration build at a time Wed, 21 Jul 2010 04:50:11 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: simpsonjulian http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/comment-page-1/#comment-401 simpsonjulian Sun, 06 Sep 2009 22:02:53 +0000 http://www.build-doctor.com/2009/08/17/deployment-is-the-goal#comment-401 Gary, thanks for the comment. I wouldn't shoot you down. The moment a dev team thinks that testing is someone else's problem, the rot sets in. Or the build, for that matter. Gary, thanks for the comment. I wouldn’t shoot you down. The moment a dev team thinks that testing is someone else’s problem, the rot sets in. Or the build, for that matter.

]]> By: Gary http://www.build-doctor.com/2009/08/17/deployment-is-the-goal/comment-page-1/#comment-402 Gary Sun, 06 Sep 2009 02:28:29 +0000 http://www.build-doctor.com/2009/08/17/deployment-is-the-goal#comment-402 Nice piece. There's a reason why companies, and even volunteer projects, don'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'm not a developer, so it's easy for me to say, but the better the dev team I've worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down.... Nice piece. There’s a reason why companies, and even volunteer projects, don’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’m not a developer, so it’s easy for me to say, but the better the dev team I’ve worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down….

]]>