Can we get a 0.18 release?

[zsiddique]

We are currently using the 0.18.0.pre-release to fix this issue, #696. But it seems with the changes in Rubygems you can no longer use pre-release to satisfy dependencies unless you pass the --pre flag. This issue was brought up almost a year ago so I think it would be safe to cut a release now.

[tarcieri]

There are still some open issues I'd like to address, and I haven't had time to go through and put together a proper changelog since it's been so long since the last release.

I'm also pretty busy right now, so I'm not sure if I'll even be able to look at this for another couple weeks.

If you're interested in helping out by fixing some of the open issues, I can provide some more direction.

[zsiddique]

Do we have a filter/list for open issues on the 0.18.0? I see the project for 0.18.0 but. IMHO if this project is stalling its best to address only bugs against 0.18pre and cut a release and the future can be figured out then.

[tarcieri]

I can tag the 0.18-specific regressions. There are a few of them.

[zsiddique]

So we are not blocked on fixing all the 0-18 regression I have created a PR for the fix in #696 to be applied against the 0-17-stable branch. You think this is something you guys can check out quickly and take a look. This would fix this issue for us: launchdarkly/ruby-server-sdk#79

[tarcieri]

@zsiddique there's a 0.18.0.pre2 release out... mind helping test it?

[zsiddique]

We ended up refactoring our codebase and removing celluloid

[tarcieri]

Closing in favor of #789