Please use semantic versioning

Question

Please use semantic versioning

Closed this issue 9 years ago · 8 comments

petercolberg commented 9 years ago

Please use semantic versioning:

Answer 1 · 2016-04-03T18:05:23.000Z

What API break where you burned by and when?

Answer 2 · 2016-04-03T18:05:43.000Z

("What API break this library", I mean)

Answer 3 · 2016-04-03T18:12:22.000Z

It would make distribution packaging of your software much more convenient if you could tag releases.

Answer 4 · 2016-04-03T18:15:12.000Z

Are you doing that? What for?

You're fine with just some tags? Does it need to work with the go tool?

Answer 5 · 2016-04-03T18:26:36.000Z

Oh, hope I didn't come off as brusque. Just want to understand exactly what you want. The original issue isn't enough to go off of.

Answer 6 · 2016-04-03T18:48:33.000Z

Debian packages each Go package repository as a separate Debian source package. In this case, your package has been included in Debian as a dependency of acmetool. The version of a Debian package includes an upstream part (e.g. "1.0.0") and a Debian part (e.g. "-1"). If an upstream author does not tag releases, we need to make up an upstream version number based on the git commit and date, which yields unwieldy versions that are cumbersome to compare.

All you would have to do is regularly tag releases, which yields handy Debian package versions and makes it easy to automatically notice new upstream releases using the Debian package tracker.

Answer 7 · 2016-04-04T04:57:06.000Z

Done. Thanks!

Answer 8 · 2016-04-04T05:05:28.000Z

Thanks! A small detail: For semantic versioning you probably want to start with v1.0.0 for the first tag.