0.12.3 not on master

[HelloGrayson]

I see 0.12.2 on master, but not 0.12.3, even though it's released:

https://github.com/Masterminds/glide/releases/tag/v0.12.3

Looks like glide.go still contains:

var version = "0.12.0-dev"

Furthermore, it looks like https://github.com/Masterminds/glide/tree/Release-branch-0.12.x is several commits ahead of master. Why not treat master as the latest release?

[HelloGrayson]

For the 0.12.3 tag, version.go still shows var version 0.12.0-dev...

glide/glide.go

Line 37 in 8460774

var version = "0.12.0-dev"

:(

[HelloGrayson]

@mattfarina what is actually on master?

[franciscocpg]

@breerly, maybe this is useful?
#616

[mattfarina]

@breerly is the tag not being on master a problem?

glide.go on master should be bumped. Good catch. I'll fix that.

There is a release branch for 0.12.x changes to keep with semver while we work on master with breaking changes.

[HelloGrayson]

@mattfarina I was expecting Glide to do something like:

1. Latest release is always on master
2. Releases are made off of master
3. Changes for the next release aggregate in another branch
4. That branch gets merged into master when ready for a new release

#631 should keep us on track going forward.