Cut a new release

[ioquatix]

@rhenium can we make 2.2.0 release soon?

[jdhollis]

Any ETA on the next release?

[ioquatix]

Hopefully soon.

[nikitarub]

Having problems with #259
Waiting for release.
What's the next release date?

[jdhollis]

*bump*

[ioquatix]

Because we've accepted a large number of PRs, I need to do a full code review before doing the next release, which will be a minor version bump. In addition, I'm not completely clear how we manage releasing this code independently of MRI, I need to investigate further.

@mame is there some process? Can we just release updated gem?

[bdewater]

Bumping again is there's a month left before the next Ruby version is released.

@ioquatix I believe that is the process as documented here: https://github.com/ruby/openssl/blob/51181247a238b1fb148dad15b6fd2fa1471fc06e/CONTRIBUTING.md#relation-with-ruby-source-tree

[ioquatix]

I have kicked this process off internally a week ago but the wheels are slow... will post an update once I know more. Thanks for the link @bdewater

[ioquatix]

@rhenium I am going to meet @hsbt this week at Asakusa.rb - it would be great to do a release that day. Do you have time to meet up?

[hsbt]

I start to migrate this repository into ruby-core at ruby/ruby#2693

At least, We should resolve the test failure on ruby-core repository.

[davispuh]

When new release could happen? There's several PRs merged in master which haven't been released. And last v2.1.2 release is a year old.

[ioquatix]

What was released in 2.7.0?

[jdhollis]

Judging by the release notes, nothing new as far as the openssl gem: https://www.ruby-lang.org/en/news/2019/12/25/ruby-2-7-0-released/

[ioquatix]

@hsbt can you explain the status of the current release?