please use git-tags

[Finkregh]

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

[sebsauvage]

You mean the README.md ?

[Finkregh]

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

tags as in 'man git-tag'

[marienfressinaud]

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]

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 https://github.com/sebsauvage/Shaarli/issues/79

[e2jk]

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

[nodiscc]

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!