Feature branch created after finishing a release (gitflow) should inherit the develop branch version

[bmmathe]

Feature branch created after finishing a release (gitflow) should inherit the develop branch version. Fixes #788.

[bmmathe]

Here is a real world scenario of the issue I'm trying to reproduce in the test.

We use gitflow to manage our SDLC. Release branches are created before we merge into master using SourceTree's Git Flow button. We "Create Release", commit the branch, and then push. If tests pass on that release branch and no further changes are necessary we "Finish Release" which merges the release branch into master and develop. We also tag the master commit with the production version. Develop commits after the merge increment the version number properly however feature branches do not increment properly. This seems to be only the case if there was no commit on the release branch. If there is a commit on the release branch it seems like feature branches do get the appropriate version number.

Here is a screen shot of the versions that GitVersion is creating.

And here is the commit graph.

[asbjornu]

@bmmathe Thanks for this! But can you please rebase on master so it gets the fixes in #876 that ensures the Travis build is run?

[JakeGinnivan]

This will be fixed by #832

One of the changes this this branch makes is to change the tag on develop to alpha instead of unstable. I am not sure if this should be released as a Minor release. Thoughts?