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?

[hsbt]

There is no progress.

So, Originally ruby/ruby#2693 is your work, not me.

[ioquatix]

@hsbt thanks, I will sort it out.

[ioquatix]

Okay, so most/all of the changes in the Ruby source code have been down streamed now.

In order to get to a 2.2.0 release, we need to address all the outstanding issues here: https://github.com/ruby/openssl/milestone/1

If you have time to help with this, please jump into an issue.

[hsbt]

@ioquatix

The current master branch was broken with the Windows platform. You should fix it before releasing 2.2.0.

see https://github.com/ruby/ruby/runs/322277594#step:10:1431

[ioquatix]

Thanks I will check

[bdewater]

In order to get to a 2.2.0 release, we need to address all the outstanding issues here: https://github.com/ruby/openssl/milestone/1

IIRC before the Ruby 2.7 release window was missed that list was a lot smaller. Is there a reason to push back the next release even further once the Windows build is fixed? To me it seems having a release as soon as possible and syncing with Ruby trunk would be preferable over more/continued drift. Plenty of valuable stuff ready to be released as well.

[jdhollis]

This release has been lingering for quite a while. I don't know what the typical process is, but is there something I can do to help ship this?

[ioquatix]

https://github.com/ruby/openssl/milestone/1

[jdhollis]

Ok. So if I understand you correctly, we just need to close the issues referenced in that milestone.

Is there a way forward where we vet and ship the changes already committed to master in a point release?

[ioquatix]

There is so much stuff that has not been released for so long, so it will require a bit of effort but yeah it’s very close.

[jdhollis]

What is the process for preparing a release?

[hsbt]

Again, At least, we need to fix ruby/ruby#2693 with the master of ruby/openssl.

[rhenium]

A blocker is OpenSSL::SSL::SSLContext#add_certificate_chain_file. It has a pending change and I don't want to include it in an incomplete state.

The initial implementation in commit 46e4bdb was not really useful. The issue is described in #305. #309 extended it to take the corresponding private key together. However, the new implementation was incompatible on Windows and was reverted by #320 to the initial one.

(The prerequisite to implement it in) an alternative way is #288, and it's still cooking.

[jdhollis]

I still think it's worth putting out a point release to get the other changes out.

I've got a client waiting on a change I committed last summer—it’s a blocker to the release of two open source libraries.

[ioquatix]

A blocker is OpenSSL::SSL::SSLContext#add_certificate_chain_file

We can push that to the 2.3 release.

[rhenium]

v2.2.0 is now pushed to rubygems.org.