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
1.0 release #570
Comments
Not particularly concrete plans at present. I do my best to maintain/operate it as stable even now (treating it pretty much like it is already 1.0), but actually calling it that would communicate a lot more. My hesitation has been that it seems like if there are breaking changes to make, now would be the time to do it (pre-1.0). But as those changes seem continually to not happen, and as 2.0 could just as easily be cut to communicate that, perhaps I should just pull the trigger. |
I think it's time to let the baby fly :) Excon is the best ruby http library and I've used them all. Bringing it to On Wed, 25 May 2016 18:55 Wesley Beary, notifications@github.com wrote:
|
One breaking change that I'd be happy to see is the one you outline here: #384 (comment) Another breaking change that I think would be good is dropping support for ruby < 2.0 |
@sandstrom yeah, I would almost assuredly drop default port (or at least switch the default to be omitting). Dropping old ruby support would definitely make our lives easier as well, though I'm not sure what the right cut-off is (guess we'll have to make that judgement call at the time we make the release). |
This issue has been automatically marked stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions. |
Pinning, just need to carve out some time. |
Closing as dup of #295 |
Any plans on releasing version 1.0 ?
Excon is pretty stable and it would be nice to benefit from semver (if you follow it) by marking the current release as stable.
The text was updated successfully, but these errors were encountered: