-
Notifications
You must be signed in to change notification settings - Fork 32
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
Ownership transfer of JrJackson to Elastic/Logstash org #86
Comments
Many thanks @guyboertje ! To be able to publish new versions of jrjackson, can you also provide |
Hey João,
I did that. Ruby gems sends an email to the new owner address. Check there
I suppose, unless you know a better way.
I used Ruby gems at elastic.co
Guy
…On Thu, 21 Jan 2021, 15:02 João Duarte, ***@***.***> wrote:
Many thanks @guyboertje <https://github.com/guyboertje> !
I'll soon do a transfer to Elastic and reach out to some of the owners of
gems that depend on this one.
To be able to publish new versions of jrjackson, can you also provide rubygems
at elastic.co rubygem ownership?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAUXMC2ETE5SWXPREFEFHTS3A6X3ANCNFSM4WLIGGTA>
.
|
Awesome, I logged into the email and ack'ed it. Many thanks again :) |
@jsvd Hello, I have the same question, when shall we use Jackson version 2.12 in logstash since CVE-2020-28491? Thanks a lot. :) |
As I have retired from software development work and am fully occupied with other things, it is time to transfer ownership of this project to the biggest users of it i.e. Elastic/Logstash.
I have sent an invite to @jsvd to be a collaborator and invited the elastic rubygems user as an owner of the rubygems entry.
Joao will action the transfer on github and complete the invite email from the rubygems server.
Lokking at the Rev deps on rubygems there are two projects that use jrjackson with recently published gems (<3 months), it would be good etiquette to inform the project owners of this change (they may or may not see this issue)
Hugs,
Guy
The text was updated successfully, but these errors were encountered: