-
Notifications
You must be signed in to change notification settings - Fork 407
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 Provide Annotated Release Tags #30
Comments
Yep, more than happy to. My versioning strategy to date was add a tag once because someone asked once 😄 . Given the momentum behind the dep project I think I'll adopt semver, and add annotations as part of changing (ie actually having) a versioning plan. |
Excellent, thanks! |
BTW I've gone and replaced the existing tags with annotated one already. |
Thanks very much for doing that! (for the record, that's become a generic stub at the bottom of many and isn't meant to be rude) |
This package is used by Gitea which is a package I'm currently working to get into Debian. This means I get to do a review of all build dependencies. While working through your project, I saw that tags are used to mark releases, but they are not being annotated.
Unannotated release tags end up causing some headaches for packaging systems that monitor upstream activity--mostly for new releases--because the information is missing from 'git describe'. To annotate a tag, it just needs the -a flag passed. (git tag -a).
If you're willing to, it's possible to update the current tags (or just latest) with annotation. I've included some links [1] [2] that explain the process.
If you choose not to update tags, it would still be hugely appreciated if you could use annotated tags in the future.
[1] http://sartak.org/2011/01/replace-a-lightweight-git-tag-with-an-annotated-tag.html
[2] http://stackoverflow.com/questions/5002555/can-a-lightweight-tag-be-converted-to-an-annotated-tag
The text was updated successfully, but these errors were encountered: