-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Make old tags #372
Comments
Thanks @ashawley. If I had any tags floating around they'd now be on an old machine, so feel free to publish those tags if you'd like. My only opinions on versioning are abiding to semver : ) For future releases it'd be great to start publishing tags + a GitHub release with a quick summary as you've done so here 👍. |
Cool, thanks. I agree on semver and agree that there should be release notes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
John,
I was thinking of publishing the following version tags since the last release, v2.9.0. I wasn't sure if you had some tags locally you hadn't pushed, or if you had opinions on version policy. If and when I finish the Gem work in #334 and we start publishing gems, versions will be important for tracking the changes, so it would be nice to keep them going as you had been.
Thanks,
Aaron
ddb6925 v2.9.1
02b72b6 v2.10.0
4fbfb87 v2.10.1
ded27ea v2.10.2
The text was updated successfully, but these errors were encountered: