Versioning and global tool deployment

[michael-emmi]

This PR aims to automate the publishing of dotnet global tools for Corral.

[michael-emmi]

@bkragl @zvonimir @akashlal thoughts about this one?

(Basically this replicates the versioning and releasing we have built for Boogie.)

Question for @akashlal: since Corral is currently unversioned, what version should we start at?

• fresh at v1.0.0
• matching Boogie at v2.4.4
• something different altogether?

[zvonimir]

To me it makes sense that this should be done for all tools that depend on Boogie, and so it is awesome that you are doing this. I can't really comment on the details of the implementation.

About the version number, I guess I would start with v1.0.0. I don't see a good reason to start with the current version of Boogie.

[michael-emmi]

About the version number, I guess I would start with v1.0.0. I don't see a good reason to start with the current version of Boogie.

Ok, then let’s make sure to include #major in the first line of the merge commit message — that should generate the tag v1.0.0.

[bkragl]

LGTM! I can compile on my machine. Perhaps the new build instructions should be added to the readme file. In particular this step I found in the Travis configuration:

# Attach HEADs in submodules to appease GitVersion
git submodule foreach 'git branch -d master && git checkout -b master'

[michael-emmi]

Perhaps the new build instructions should be added to the readme file.

Good idea, I’ll do that.

[michael-emmi]

NOTE: be sure to include #major in the first line of the merge commit when merging this.

[michael-emmi]

@akashlal any objections to this PR?

[michael-emmi]

Oh crap I merged by accident…

[michael-emmi]

Confirming with @akashlal this is OK; otherwise we can always create a revert PR.

[akashlal]

Looks good, thanks!