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

Please use semantic versioning #25

Open
petercolberg opened this issue Apr 3, 2016 · 1 comment
Open

Please use semantic versioning #25

petercolberg opened this issue Apr 3, 2016 · 1 comment

Comments

@petercolberg
Copy link

Please use semantic versioning:

@petercolberg
Copy link
Author

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.

ThinkChaos pushed a commit to ThinkChaos/pflag that referenced this issue Feb 28, 2022
Add new FlagSet.Get{Int,String,...} accessor functions
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

No branches or pull requests

1 participant