-
Notifications
You must be signed in to change notification settings - Fork 160
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
Gem ship. #61
Comments
I send transfer offer to |
I contacted the current owner at mbailey/openssl#1 and @mbailey agreed with releasing the gem namespace. |
oops. Should I continue to transfer negotiation instead of you? And I sometimes request to remove stdlib protection to rubygems admins. see. rubygems/rubygems.org#1273 |
commented mbailey/openssl#1 (comment) |
I guess we still need to decide a version number? |
@rhenium I've been promoted openssl owner by rubygems admins. Can you give your mail address on rubygems? |
@hsbt Thank you always! My email is k(at)rhe.jp. |
@rhenium I added owner grant to you. If you are ready to ship openssl gem, I'm going to request to remove openssl from rubygems blacklist. |
@hsbt Thanks! It looks like openssl is already excluded from the list, at least in the source repository. rubygems/rubygems.org@6e74bd9 I think we can release now if only we decide the version number. |
@hsbt @rhenium お疲れさまです! I will review #59 and commit my changes to the documentation. Regarding the
However, there is some duplication between the updates and compatibility list. I will review this too, but first I think we could split it up similar to Rails release notes as such:
Changes would include the following:
One other idea is after the release is made, we should consider moving the Thanks for taking the time to work on this and prepare the release! I will submit my thoughts in the form of a patch :) |
@zzak Thanks! That's a great help.
I think we can just append on top, each release note would be smaller than Ruby. Maybe I should have named it |
Append is also fine! Let's go with |
@zzak Thank you! It looks much nicer! Do you have suggestions on changes in README.md and CONTRIBURING.md? |
@rhenium Thanks, I will review. |
|
OpenSSL 1.1.0 was just released today, and Ruby/OpenSSL looks working fine with it: https://travis-ci.org/ruby/openssl/builds/155282416 Is there still a blocker for the release? |
There is no blocker for me |
I have no blockers, version 2.0.0 sounds fine. Let's yank the current gems from rubygems.org and cut a pre-release? |
I think so! Can I do that? |
@rhenium Yes, if you are authenticated on rubygems.org, via the
And to publish (after updating
For example if you wanted to choose "beta1" as the first pre-release. |
Just pushed openssl-2.0.0.beta1: https://rubygems.org/gems/openssl |
Imported to trunk at: ruby/ruby@c9dc016 |
Linkify in #69 |
@tenderlove BTW bro, the |
@zzak ALPN and ECDH callback are part of Ruby 2.3 (though they aren't in doc/NEWS-2.3.0). |
Gem ship is done. ref. https://rubygems.org/gems/openssl/versions/2.0.0.beta.1 |
I found some blocker for
openssl
gem release.openssl
. https://rubygems.org/gems/opensslopenssl
from rubygems blacklist . https://github.com/hsbt/rubygems.org/blob/master/lib/patterns.rb@rhenium @zzak If you have some blocker, Please note this issue. I will try to solve it.
The text was updated successfully, but these errors were encountered: