please tag formal releases

[onlyjob]

Please consider assigning version numbers and tagging releases. 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.

Versioning provides safety margin for situations like "ops, we've made a mistake but reverted problematic commit in master". Presumably tagged version/release is better tested/reviewed than random snapshot of "master" branch.

Thank you.

See also

• http://semver.org/
• https://en.wikipedia.org/wiki/Software_versioning

[onlyjob]

Just closing without resolution or comment??

[jonboulle]

FWIW we need this for rkt releases on Debian :-)

On Wed, Mar 30, 2016 at 1:11 PM Dmitry Smirnov notifications@github.com wrote:

Just closing without resolution or comment??

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/peterbourgon/diskv/issues/27#issuecomment-203381600

[peterbourgon]

Just closing without resolution or comment??

Without a concrete use case, this request represents a change in my process to no perceivable benefit. That is, my Go projects don't have formal releases, and I'm keen to keep it that way. I'm all on-board with semver conceptually, but in the Go universe there are no tools or practices that leverage it usefully.

FWIW we need this for rkt releases on Debian :-)

Ah! A concrete use case :)

[peterbourgon]

https://github.com/peterbourgon/diskv/releases/tag/v1.0.0

[onlyjob]

Thank you, Peter! :)