Open gfairchild opened 10 years ago
Yeah, I might take some important ones after the fact.
But I am a real github noob. We've been using SVN at work (and prior to that CVS).
2014/1/21 Geoffrey Fairchild notifications@github.com
I know releases are discussed and provided herehttps://bitcointalk.org/index.php?topic=167229.0, but it would be great if releases were also tagged here on GitHub. That way, if mega goes down, or bitcointalk.org goes down, official releases will still be available (although without binaries). Having source code that sits alongside each release would be really nice.
— Reply to this email directly or view it on GitHubhttps://github.com/cbuchner1/CudaMiner/issues/71 .
It's really easy. Whenever you're ready to release a new version, you just create a "tag" using git. http://git-scm.com/book/en/Git-Basics-Tagging describes the different kind of tags. Most people, in general, use annotated tags (because of the reasons described in that link), so the last release would be tagged like this, for example:
git tag -a 2013-12-10 -m "tagging version 2013-12-10"
git push --tags
I know releases are discussed and provided here, but it would be great if releases were also tagged here on GitHub. That way, if mega goes down, or bitcointalk.org goes down, official releases will still be available (although without binaries). Having source code that sits alongside each release would be really nice.