Define version release procedure
- an official release procedure of vs components should be defined and implemented
- currently each Dockerfile has got a version, which is used by gitlab ci to tag images in the registry
- on production servers :latest tag is pulled
An option would be https://github.com/c4urself/bump2version for manually updating VERSION in Dockerfiles. In order to avoid having different "commits" as one version, gitlab.ci would push a tagged version only if the tag does not exist yet (as eoxserver travis.ci does it?) Pros:
- we have control over releases manually
Cons:
- someone has to do it