Pick and describe a release strategy

[kplaube]

Regarding the Software as a Service aspect of Tomaco, we don't need to worry too much about versioning and release. It's pretty much the concept of continuous deployment and continuous release: Once on master, and tests pass, ship it.

But regarding the aspect of open source tool, that can be downloaded (via git or as a docker image), we should start thinking about versioning our releases.

[mittmannv8]

It's a good idea.
May be we can mix the semantic versioning as release structure with gitflow workflow

[kplaube]

We already use conventional commits, so it would fit perfectly.

[kplaube]

Also, we should consider rewrite our Docker file in order to make it "production ready". One way to ensure this works is changing our Heroku buildpack to use Docker images instead of git push(es).