major (breaking change, e.g. change in docker command call convention, or if upgrading a dependency to a version with known breaking changes e.g. terraform 0.12 -> 0.13)
minor (new feature/enhancement, e.g. implement a new CLI image or improve UX/DX)
patch (bugfix)
Because we have many dependencies that we cannot control, the version should be incremented based on the changes to the akamai-docker repo, not based on dependency changes - except when obvious (e.g. terraform 0.13 upgrade).
When a version number is incremented, a git tag should be created for that version.
When a tag is created, a corresponding docker image tag should be built.
Weekly and master commit builds should update the :latest docker tag - to support "evergreen", non-production usage.
Monthly is no longer required. Recurring build no longer requires creating a timestamped tag. Users needing to pin against a version can use the semantic version.
Release notes should be generated automatically using commit messages from git history.
On code change, increment version number
Because we have many dependencies that we cannot control, the version should be incremented based on the changes to the akamai-docker repo, not based on dependency changes - except when obvious (e.g. terraform 0.13 upgrade).
When a version number is incremented, a git tag should be created for that version. When a tag is created, a corresponding docker image tag should be built.
Weekly and master commit builds should update the :latest docker tag - to support "evergreen", non-production usage. Monthly is no longer required. Recurring build no longer requires creating a timestamped tag. Users needing to pin against a version can use the semantic version.
Release notes should be generated automatically using commit messages from git history.