Skip to content
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

release 0.9.1 with warning fixes #130

Closed
ioquatix opened this issue May 3, 2018 · 4 comments
Closed

release 0.9.1 with warning fixes #130

ioquatix opened this issue May 3, 2018 · 4 comments

Comments

@ioquatix
Copy link
Collaborator

ioquatix commented May 3, 2018

Please? thanks :)
@igrigorik
Copy link
Owner

It doesn't need to block, but I was hoping we could resolve #126 (and #44), before doing next release? WDYT?

@ioquatix
Copy link
Collaborator Author

ioquatix commented May 5, 2018

IMHO, that's going to be a 0.10.0 release because it's going to break the contracts of the API. So far I'm aware that at least two people have worked around that bug by manually calling that function. I am happy to work on it further, but let's just get 0.9.1 out the door. I like small incremental releases.

@igrigorik
Copy link
Owner

Fair enough.

@igrigorik
Copy link
Owner

0.9.1 should be live on rubygems! c3e5733.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@igrigorik @ioquatix