Comments on: deployment schedules are not effective http://www.effectivedevelopment.net/2009/04/deploy-schedules-do-not-work/ Thoughts from the World Of Practical Web Development Tue, 13 Jul 2010 13:22:25 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Kevin B http://www.effectivedevelopment.net/2009/04/deploy-schedules-do-not-work/comment-page-1/#comment-2 Kevin B Thu, 02 Apr 2009 22:40:42 +0000 http://effectivedevelopment.wordpress.com/?p=22#comment-2 Another drawback to deploying code on a release schedule is that problems with one module can trigger a rollback that affects all the components in the release. You quickly learn that the more elements you daisy chain together, the higher your chances of failure. Release schedules work much better for traditional shrink-wrapped software than for the internet. Point releases are far superior for internet development, in my opinion. Problems arise when you have different groups handling code deployment and infrastructure monitoring. Wake your systems guy up a couple of times at 3am with a web server or DB locked up from newly deployed bad code and you will find yourself looking at a more rigid format for deploying code. Also at a clearly defined rollback procedure.... Read More Personally, I am a fan having the same team code, deploy and monitor, but this is not possible in large organizations. Another drawback to deploying code on a release schedule is that problems with one module can trigger a rollback that affects all the components in the release. You quickly learn that the more elements you daisy chain together, the higher your chances of failure.

Release schedules work much better for traditional shrink-wrapped software than for the internet. Point releases are far superior for internet development, in my opinion.

Problems arise when you have different groups handling code deployment and infrastructure monitoring. Wake your systems guy up a couple of times at 3am with a web server or DB locked up from newly deployed bad code and you will find yourself looking at a more rigid format for deploying code. Also at a clearly defined rollback procedure…. Read More

Personally, I am a fan having the same team code, deploy and monitor, but this is not possible in large organizations.

]]>