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

Git semver release tags #562

Closed
gdm85 opened this issue Feb 22, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@gdm85
Copy link

commented Feb 22, 2016

When using vendoring, it is also needed to pin packages to specific versions.

Would it be possible to tag releases in this git repository using semver tags?

@gdm85 gdm85 changed the title Git semver tags Git semver release tags Feb 22, 2016

@zellyn

This comment has been minimized.

Copy link
Contributor

commented Feb 22, 2016

+1 Docker, CoreOS, Kubernetes and many other prominent Go projects are doing this.

@bradfitz

This comment has been minimized.

Copy link
Contributor

commented Feb 24, 2016

I vote no. Pin the hash you need after it's tested with your application. It's not like we're maintaining many branches. There is exactly one.

@gdm85

This comment has been minimized.

Copy link
Author

commented Feb 24, 2016

@bradfitz tags make sense if you have a reported version, releases and a CHANGELOG, which I see you don't. So maybe one should first politely ask for those.

@bradfitz

This comment has been minimized.

Copy link
Contributor

commented Feb 24, 2016

Sorry, this still sounds like a solution in search of a problem. git log is a pretty good changelog.

@gdm85

This comment has been minimized.

Copy link
Author

commented Feb 24, 2016

@bradfitz wow. That means versioning software is such an useless flick. How could I not see this before 😉 Thanks anyways.

@gdm85 gdm85 closed this Feb 24, 2016

@bradfitz

This comment has been minimized.

Copy link
Contributor

commented Feb 24, 2016

It makes sense when you're doing releases and maintaining branches. It doesn't makes sense when you're doing neither. Maybe one day, but not yet.

@onlyjob

This comment has been minimized.

Copy link

commented Jun 9, 2016

Tags/releases are useful for downstream package maintainers (in Debian and other distributions) to export source tarballs, automatically track new releases and to declare dependencies between packages. Read more in the Debian Upstream Guide.

Versioning provides additional benefits to encourage vendoring of a particular (e.g. latest stable) release contrary to random unreleased snapshots.

Please consider tagging releases.

Thank you.

See also

@lock lock bot locked as resolved and limited conversation to collaborators Sep 26, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.