-
Notifications
You must be signed in to change notification settings - Fork 27
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 a new release #29
Comments
I'll be looking to get #6 done before the release happens. |
Is this still true? It's now >4 years since the latest "official" release |
I apologize for the lack of communication, I might as well give a little postmortem here.
@AlexWayfer I'll add you as a gem maintainer if you can provide me your information to do so. Feel free to merge/release with whatever changes you have pending. Also that PR above just needs some extra test cases to pass (and even might be outdated at this point) |
Em… of course, but my info is public everywhere. I'd like to try to continue maintain this gem.
I can understand this. And I have a little more experience now after working with I wish you luck with your life, even without Ruby. Thank you for your work. I'd like to have access to push this gem to RubyGems.org |
NEWS: I've been added as the gem maintainer (thanks to @mauricew)! I've merged open PRs meanwhile. So, the new release is near. I think I'll make it in the current state, without fresh end-points from open issues. If you need for them — write there, or PRs are welcome. |
It has been done. Meet the new 1.0 version. #6 and #30 have been completed. #39 has not. There are always new end-points for us to implement. Asking and pull requests are welcome. I have in plans some management with data classes, like a base class, etc. But I left it after v1.0. It works for now, and I'm kind of tired now. |
There were many changes, including client headers and authentication, so let's make a new release (0.5.0, I guess).
The text was updated successfully, but these errors were encountered: