Docker naming scheme

As discussed in https://github.com/GitTools/GitVersion/pull/1571#discussion_r249751741, it would be beneficial for us if GitTools didn’t have 4 different repositories for GitVersion:

• gitversion-fullfx
• gitversion-dotnetcore
• gitversion
• libgit2sharp-mono

I believe having these four options publicly available makes it unnecessary hard to choose which Docker image to use and the naming standard of the tags in each repository is also a bit hard to understand.

I think it would be beneficial to us and our users if we ended up with just one Docker image and associated repository, simply called gitversion and that the tag naming scheme of this repository followed that of NGINX, which would give us the tag format {version}-{platform}-{framework}. For example:

• 4.0.0-centos
• 4.0.1-beta2-debian-fx
• 4.0.0-beta15-windows-dotnetcore
• latest-ubuntu
• latest-windows
• stable-ubuntu
• stable-windows

I have a whole heap of unanswered questions related to this:

• Is this at all possible?
• Can we obsolete repositories so they aren’t listed, but still have their contained images be usable for those who are using them?
• Can we clean up the visible tags of a repository without making the images for those tags unavailable?
• Will the proposed naming scheme support all the different variations we want and need?
• Are there anything I haven’t thought of?

[asbjornu]

Ok, I agree. {version}-{os}-{distro}-{targetframework} it is, then.

[asbjornu]

I think we should also include the framework version, so that we can support dotnet core 2.1 and 2.2 as well as for the full framework 4.7.2

Can’t we use the same framework notation as the one used in MSBuild’s <TargetFramework>? Such as:

• netcoreapp2.1
• netcoreapp2.2
• net472