Continuous updating for kb2647516

You might have the marketing folks who are going to promote it double-check that it does what they expect.

continuous updating for kb2647516-5

Most of these changes are supposed to be “side effect free” although few traditional development teams actually achieve that level of quality.

So the first shift in mindset required for continuous deployment is this: if a change is supposedly “side effect free,” release it immediately.

Don’t wait to bundle it up with a bunch of other related changes.

If you do that, it will be much harder to figure out which change caused the unexpected side effects.

Although this sounds similar to a staging server, it’s actually much more powerful.

Because the feature is live in the real production environment, all kinds of integration risks are mitigated.

Having evangelized the concept of continuous deployment for the past few years, I’ve come into contact with almost every conceivable question, objection, or concern that people have about it.

The most common reaction I get is something like, “that sounds great – for your business – but that could never work for my application.” Or, phrased more hopefully, “I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software? I understand why people would think that a consumer internet service like IMVU isn’t really mission critical.

So asking customers if they’d like to receive new releases more often usually leads to a consistent answer: “No, thank you.” On the other hand, you’ll get a very different reaction if you ask customers “next time you report an urgent bug, would you prefer to have it fixed immediately or to wait for a future arbitrary release milestone?

Tags: , ,