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 git-tags #77

Open
Finkregh opened this issue Apr 16, 2013 · 6 comments
Open

please use git-tags #77

Finkregh opened this issue Apr 16, 2013 · 6 comments

Comments

@Finkregh
Copy link

please use git-tags to mark versions as i did in https://github.com/Finkregh/shaarli

@sebsauvage
Copy link
Owner

You mean the README.md ?

@Finkregh
Copy link
Author

nope, i mean e.g. https://github.com/Finkregh/shaarli/tree/v0.0.40 :)

tags as in 'man git-tag'

@marienfressinaud
Copy link

Yes, I agree with this request: when you release a new version, just use git tag -a vX.X.X for example and then, git push --tags
So you can easily provide different versions of Shaarli and use the "release feature" of Github (see https://github.com/sebsauvage/Shaarli/releases)

@nodiscc
Copy link

nodiscc commented Oct 19, 2013

hey when do we get a nice release with the recent changes? like `git tag -a 0.0.42; git push --tags".
This would also close #79

@e2jk
Copy link

e2jk commented Jul 20, 2014

This would be very useful as well for the Debian package to detect when new versions are officially released.

@nodiscc
Copy link

nodiscc commented Jul 20, 2014

Moving this from #195:

Hi, could you please provide tags for releases of your (nice) software?

git tags help keeping track of new releases, features and security fixes for users and contributors. Users/admins can check the "Releases" tab of your github project to see if their install is up to date. They can also subscribe to the RSS feed at https://github.com/sebsauvage/Shaarli/tags.atom

A guide on basic tagging is available at http://git-scm.com/book/en/Git-Basics-Tagging but it boils down to this:

git tag v0.1 #your release number here
git push --tags

New tags could be issued when your software has received several new tested features and is ready for release, or when a critical security fix has been issued. An example of great tagging: https://github.com/chyrp/chyrp/tags

This repo currently has no tags, so may you tag the lastest revision as you like? 0.0.41 or 0.0.42 would be fine. Thanks!

pikzen pushed a commit to pikzen/Shaarli that referenced this issue Jan 21, 2015
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

5 participants