To deploy versus to release

Monday, April 10, 2017 1 Comments

If you read our previous blogpost about how we do trunk based development with Plastic SCM, you probably have a few unanswered questions.

This blogpost is the second in the series and covers something we find interesting: the difference between deploying and releasing.

To deploy versus to release

This is something interesting and worth considering, especially for non-native English speakers like me.

You can deploy a new feature without releasing it.

Yes, you can put your new version in production, but it can be disabled, waiting to be released.

The DevOps "handbook" explains it better, but you get the point.

And the important thing is: yes, deploy as much as you can, but you control releases. Usually, release will happen at deploy time, but in very "trunk-based development fashion", sometimes you will hold the release to start unveiling it only to certain users. Very web-like, but also doable for on premise servers and even desktop apps.

1 comment:

  1. That's very true, and most teams handle release dates and use a code to cypher major, minor, build number and so forth but the final customer only perceives the changes when they are actually released, and that's kind of a management (or sales) decision.

    IMHO, the important thing for us, technicians is: deploy, more than release. When it's about a product and not a custom-made software we could distinguish between public and private releases to see the difference between deploy and release. D'you agree?

    ReplyDelete