Skip to content

Latest commit

 

History

History
34 lines (25 loc) · 2.33 KB

VERSIONING.md

File metadata and controls

34 lines (25 loc) · 2.33 KB
Raw

About Versioning

This guidelines apply to versioning of docker images in mailserver2 repos:

  • mailserver
  • debian-mail-overlay
  • postfixadmin
  • rainloop

Historically the old hardware/debian-mail-overlay image seemed to be versioned after rspamd it includes. However, apart of rspamd the image contains a lot of other differently versioned software. In this regard, it's more logical to have an independent version, and note down the version of individual software component in the commit messages and/or release history. Where possible, use Semantic Versioning.

For rainloop and postfixadmin it makes sense to continue to version the images after the respective software versions, since it's not likely that they may require a version bump for any other reason.

In certain case it's also possible for the Dockerfile itself to change without individual components updates. Finally, it could be that the Dockerfile does not change either, but the change is effected by update in an upstream software repository, for example clamav updates in mailserver are handled this way.

Follow these steps when an update is ready to be pushed to Docker Hub:

  • Make sure you are on the master branch and that the HEAD is pointing to the lastest commit (git checkout master). git log --name-status HEAD^..HEAD should give you the same commit number that the latest commit you see at https://github.com/mailserver2/mailserver
  • Tag the current GitHub commit in the mailserver2 repo with the next version, e.g. git tag -a v1.0.1 -m "update postfixadmin to version 1.0.1, ... other changes here"
  • Push tags with git push --tags
  • Create a release corresponding to the tag under "Releases" section of GitHub repository. Make sure to include change log, when creating a release
  • Build the new docker image (see below for an example)
  • Label it with the version you tagged the current commit with
  • Push this image version with the label above as well as with the latest label

Build Example

docker build . -t debian-mail-overlay
docker tag debian-mail-overlay mailserver2/debian-mail-overlay:0.0.0
docker push mailserver2/debian-mail-overlay:0.0.0
docker tag debian-mail-overlay mailserver2/debian-mail-overlay:latest
docker push mailserver2/debian-mail-overlay:latest