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.

Sign up for GitHub

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

Jump to bottom

1.0.2 release #250

Closed

igrigorik opened this issue Jun 28, 2013 · 3 comments

Member

igrigorik commented Jun 28, 2013

Any blockers that we should address prior to pushing 1.0.2 to rubygems? No open bugs, but just to make sure.. :)

Contributor

xentek commented Jun 28, 2013

1 similar comment

Member

nolman commented Jun 29, 2013

Member Author

igrigorik commented Jun 29, 2013

Doh.. of course, I meant 1.0.3.. which is now up on rubygems. :)

igrigorik closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment