Update projects to use new GitVersion.yml file

[gep13]

As suggested by @Jericho

[gep13]

This is the suggestion:

mode: ContinuousDelivery
branches:
  releases?[/-]:
    mode: ContinuousDeployment
    tag: rc
  dev(elop)?(ment)?$:
    mode: ContinuousDeployment
    tag: alpha
  hotfix(es)?[/-]:
    mode: ContinuousDeployment
    tag: beta
ignore:
  sha: []

[Jericho]

FYI: when we upgrade to GitVersion 4.0, the content of the yml file would need to be changed to:

mode: ContinuousDelivery
branches:
  release:
    regex: releases?[/-]
    mode: ContinuousDeployment
    tag: rc
  develop:
    regex: dev(elop)?(ment)?$
    mode: ContinuousDeployment
    tag: alpha
  hotfix:
    regex: hotfix(es)?[/-]
    mode: ContinuousDeployment
    tag: beta
ignore:
  sha: []

[pascalberger]

Whats the reason to use different tags for release and hotfix branches? IMHO its confusing for the user if there is eg. 1.2.0-rc.1 but afterwards 1.2.1-beta.1.

[gep13]

@pascalberger I am not sold on this part of the suggestion either. Having alpha from develop, and beta from release and hotfix also makes sense, then if you want to release an rc you can tag the hotfix or release branch with this name.

[gep13]

@Jericho did you have any additional comments on this?

[Jericho]

Only comment is that this setup works great in my projects that's why I recommend it.