Release version 1.0.0

[sferik]

Excon turn 4 years old at the end of this month. Many popular gems (notably fog) depend on Excon. Seems like it's about time to declare a stable, public API.

From the SemVer FAQ:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

[geemus]

Strong points all around. There is a 1.0.0 milestone here: https://github.com/geemus/excon/issues?milestone=1&page=1&state=open. I haven't been making a particular concerted effort there though and some of it may be out of date. I just thought there might yet be some potentially breaking changes to get out of the way before the 1.0.0 stamp went on it. I'll try to start making some time to move this forward again though, as I agree it is rather long overdue.

[stale]

This issue has been automatically marked stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

[sandstrom]

Copying over comments from #570.

Two breaking changes that I'd be happy to see:

• Fixing use of Addressable as :uri_parser, as mentioned in Excon doesn't work with :uri_parser => Addressable::URI #384 (comment) This works in 0.62! 💯
• Dropping support for older rubies, at least 2.0 (but maybe even < 2.3). Ruby themselves have stopped maintaining 2.2.

There are probably other changes for 3.0 that you'd want to add. For example, perhaps there are some rarely used parts of the library that could be removed?

Looking forward to 1.0!

[geemus]

@sandstrom good call (looks like the copy didn't work though). Thanks!

[geemus]

@sandstrom now I see the rest of the comment. Yes, dropping earlier ruby support makes a ton of sense. I've added the pinned tag to a few things that are also candidates for inclusion, but haven't made an explicit 1.0 plan quite yet.