Delivering software - Responses

Re: Anti-pattern: The release vehicle.

Michael Wasser — Sun, 04 Jul 2010 18:56:16 GMT

Very interesting ideas! Just a few quick thoughts: Might this model actually disincentivize larger more invasive change that may sometimes be necessary for more strategic architectural changes? I'm all for automating as much as is possible (as opposed to manual qa) and having the ability to have deployable/tested version of a product on a regular basis -- but actually deploying on a very regular basis seems as if it may become a road block to large change after a product has been initially released. Also, I would imagine that if you cannot guarantee all consumers of a product are working with the same product version, having a new version every two weeks could become a nightmare for a support organization (imagine a support rep needing a hotfix for 20 releases of a product instead of 1 or 2). In my mind there are clear benefits to the model you suggest here but there are also pitfalls. Thoughts?

Re: Anti-pattern: The release vehicle.

Andrew Rendell — Tue, 23 Feb 2010 21:39:40 GMT

Thanks for the positive feedback! Feel free to use the posting in any way you like. If you need any further information or clarifications just ask.

Andrew.

Re: Anti-pattern: The release vehicle.

Alex Honor — Mon, 22 Feb 2010 19:26:36 GMT

Great example of a widely used/abused practice! I would like to add it to a design pattern catalog I am just now compiling: Deployment management design patterns for DevOps.