It would be a lot easier to lock down (or roll back to a particular version) if each release was tagged. It'd also help see what the history was for that version.
Hey, I want to confirm something with you. Is the recommend order to do this: 1) push your code, and then 2) run "git tag (version)"?
Or actually, git tag -a (version) -m (message)?
I just ran git tag -a "v2.0.0" -m "v2.0.0" and pushed, but didn't seem to notice anything special happen.
Sorry, I missed your question six months ago. You need to "push --tags" in order for tags to get pushed. git is a bit braindead in that way. Alternatively, I think the new GitHub Releases stuff will set the tag up properly for you.