-
Notifications
You must be signed in to change notification settings - Fork 390
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
Comments
You mean the README.md ? |
nope, i mean e.g. https://github.com/Finkregh/shaarli/tree/v0.0.40 :) tags as in 'man git-tag' |
Yes, I agree with this request: when you release a new version, just use |
hey when do we get a nice release with the recent changes? like `git tag -a 0.0.42; git push --tags". |
This would be very useful as well for the Debian package to detect when new versions are officially released. |
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:
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! |
Make Shaarli's template W3C compliant sebsauvage#64
please use git-tags to mark versions as i did in https://github.com/Finkregh/shaarli
The text was updated successfully, but these errors were encountered: