Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix version naming convention to have 'v' prefix #986

Merged
merged 1 commit into from
May 29, 2018

Conversation

harshavardhana
Copy link
Member

This change is needed to follow vgo guidelines
put forth by Go community.

https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L6

// semantic version strings must begin with a leading "v"

Supported format style

https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L11

// vMAJOR[.MINOR[.PATCH[-PRERELEASE][+BUILD]]]

Fixes #985

This change is needed to follow `vgo` guidelines
put forth by Go community.

https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L6

> // semantic version strings must begin with a leading "v"

Supported format style

https://github.com/golang/vgo/blob/master/vendor/cmd/go/internal/semver/semver.go#L11

> //	vMAJOR[.MINOR[.PATCH[-PRERELEASE][+BUILD]]]

Fixes minio#985
@nitisht nitisht requested review from krisis and nitisht May 28, 2018 04:22
@kannappanr kannappanr merged commit 034ea46 into minio:master May 29, 2018
@harshavardhana harshavardhana deleted the fix-version branch May 29, 2018 18:10
@fd0
Copy link
Contributor

fd0 commented May 30, 2018

Sorry for jumping in here, this change seems to be not related to what I suggested in #985: It was just about the tags in the git repository for minio-go, so from my point of view (and Go's) the string in the library does not matter at all. The version is still 6.0.1, just the version tag (in git) should be v6.0.1... Not sure what to do with this, at least you know now ;)

@harshavardhana
Copy link
Member Author

harshavardhana commented May 30, 2018

Now the tag is v6.0.2 we won't be changing the old tags is that needed as well ?. The string is needed because that is used to automatically release the library.

@fd0
Copy link
Contributor

fd0 commented May 30, 2018

ah, I didn't see that earlier, that's sufficient. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants