Re: Proposal: Jenkins Core PR reviewers team

2021-04-16 Thread Oleg Nenashev 
Welcome aboard Basil! I have updated the permissions and added you to the
Jenkins Core PR reviewers team.

Just for the record, the Pull request review guidelines and other
maintainer docs are available here
.
We are always interested in onboarding more core maintainers, and everyone
is welcome to participate.

Best regards,
Oleg Nenashev


On Thu, Apr 15, 2021 at 10:35 PM Oleg Nenashev 
wrote:

> +1. I will grant Basil permissions tomorrow if no negative feedback. And
> again, thanks to Basil for all the contributions to Jenkins!
>
> On Thu, Apr 15, 2021, 22:33 Tim Jacomb  wrote:
>
>> +1
>>
>> On Thu, 15 Apr 2021 at 19:07, Mark Waite 
>> wrote:
>>
>>> +1 from me that Basil becomes part of the core PR reviewers team.
>>>
>>> On Thu, Apr 15, 2021 at 11:54 AM Basil Crow  wrote:
>>>
 I'm interested in joining the Core PR reviewers team as well.

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrnHZmDg-JmtP%2B3fO%3Df1w_uNRFevrOy9dHfsq29n0xDnA%40mail.gmail.com
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFoN%3DsiPzRHcLHJyJbs1xBqnFVAkfQONGcwcE4a90hGhw%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/0sdrcSOQW64/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifbZ_nDppzESg7VQSzM3-HKzk96V%2B7WYDP5-LFwoHZhRg%40mail.gmail.com
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCX_kb1ZB%3DQTqP%2BBpqbE37u0v%2BT4Bh4n6NKgSZZZ-1Nzg%40mail.gmail.com.

Re: Deprecating ruby-runtime

2021-04-16 Thread Oleg Nenashev 
It might work on Java 11, bit I see no much reason in even trying. If we
drop the Ruby ecosystem, Python should go as well IMHO

On Fri, Apr 16, 2021, 18:49 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> There's only a single python plugin, so I think we should include python
> in this announcement too
>
> https://plugins.jenkins.io/python-wrapper/#dependencies
>
> the install shield plugin only has 200 installs and I suspect it also
> won't work right in java 11?
>
> Gavin
>
> On Fri, Apr 16, 2021 at 7:00 AM Jesse Glick  wrote:
>
>> On Fri, Apr 16, 2021 at 6:09 AM Oleg Nenashev 
>> wrote:
>>
>>> [Regarding] removing the JEP-200 Ruby Runtime exceptions and XStream
>>> converters from the Jenkins core […] we should set a grace period, e.g.
>>> announce this change with a 6-month advance so that users have an
>>> opportunity to migrate to other plugins.
>>>
>>
>> I do not see any need to wait that long. Just do it and announce it
>> applies to the next weekly. The next LTS upgrade guide will mention this of
>> course. Users have the “opportunity” to migrate to other plugins whenever
>> they want, or simply decline to update Jenkins core.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3sVd6Qkgwq4M930_OJi%2BNVvyCjL5ubiQTGAPhK_KK3QA%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut%3Dg85m6LXLEF2rs71CvHtDjJt-nfvPdHtwtWwtyAK52g%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCvxnDfHuPakvs%2B%3DO-M%3DkV_vCEvqR6ZN3QGb0YRKCr6Wg%40mail.gmail.com.

Re: Deprecating ruby-runtime

2021-04-16 Thread 'Gavin Mogan' via Jenkins Developers 
There's only a single python plugin, so I think we should include python in
this announcement too

https://plugins.jenkins.io/python-wrapper/#dependencies

the install shield plugin only has 200 installs and I suspect it also won't
work right in java 11?

Gavin

On Fri, Apr 16, 2021 at 7:00 AM Jesse Glick  wrote:

> On Fri, Apr 16, 2021 at 6:09 AM Oleg Nenashev 
> wrote:
>
>> [Regarding] removing the JEP-200 Ruby Runtime exceptions and XStream
>> converters from the Jenkins core […] we should set a grace period, e.g.
>> announce this change with a 6-month advance so that users have an
>> opportunity to migrate to other plugins.
>>
>
> I do not see any need to wait that long. Just do it and announce it
> applies to the next weekly. The next LTS upgrade guide will mention this of
> course. Users have the “opportunity” to migrate to other plugins whenever
> they want, or simply decline to update Jenkins core.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3sVd6Qkgwq4M930_OJi%2BNVvyCjL5ubiQTGAPhK_KK3QA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut%3Dg85m6LXLEF2rs71CvHtDjJt-nfvPdHtwtWwtyAK52g%40mail.gmail.com.

Re: Deprecating ruby-runtime

2021-04-16 Thread Jesse Glick 
On Fri, Apr 16, 2021 at 6:09 AM Oleg Nenashev 
wrote:

> [Regarding] removing the JEP-200 Ruby Runtime exceptions and XStream
> converters from the Jenkins core […] we should set a grace period, e.g.
> announce this change with a 6-month advance so that users have an
> opportunity to migrate to other plugins.
>

I do not see any need to wait that long. Just do it and announce it applies
to the next weekly. The next LTS upgrade guide will mention this of course.
Users have the “opportunity” to migrate to other plugins whenever they
want, or simply decline to update Jenkins core.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3sVd6Qkgwq4M930_OJi%2BNVvyCjL5ubiQTGAPhK_KK3QA%40mail.gmail.com.

Re: Deprecating ruby-runtime

2021-04-16 Thread Oleg Nenashev 
Thanks Gavin for the announcement draft! It looks great, and I plan to 
submit a few suggestions to improve it.

Regarding the process... Should we also add heads-up about removing the 
JEP-200 Ruby Runtime exceptions and XStream converters from the Jenkins 
core (source 
)?
 
It is a reasonable next step, but it will nuke plugin users on the newer 
Jenkins cores. IMHO we should set a grace period, e.g. announce this change 
with a 6-month advance so that users have an opportunity to migrate to 
other plugins. In such a case, they may also benefit from an administrative 
monitor warning them about the breaking change (it would be a nice engine 
in general for deprecations).

BR, Oleg



On Friday, April 16, 2021 at 4:38:57 AM UTC+2 ga...@gavinmogan.com wrote:

> Draft - https://github.com/jenkins-infra/jenkins.io/pull/4256
>
> Would love some ideas on workarounds.
>
> I'll have a PR ready for update-center before may 15th.
>
> On Thu, Apr 15, 2021 at 7:14 AM Baptiste Mathus  wrote:
>
>> +1 for deprecating this. The Jenkins community should invest its time 
>> more into the future than these components that are lacking any kind of 
>> maintainership.
>>
>> Cheers  
>>
>> Le jeu. 15 avr. 2021 à 04:55, Owen Mehegan  a écrit :
>>
>>> gitlab-plugin doesn't depend on it, but gitlab-hook plugin does. It has 
>>> been unmaintained for 5 years and functionality is replaced by 
>>> gitlab-plugin and gitlab-branch-source.
>>>
>>> On Thu, Apr 15, 2021, 12:39 PM Jim Klimov  wrote:
>>>
 On April 14, 2021 6:45:30 PM UTC, Oleg Nenashev  
 wrote:
 >I am +1 for depreciation. I would recommend to make an announcement
 >blog
 >about that with e.g. 1-month advance notice, but there is no reason to
 >keep
 >these plugins around. Ruby plugin stack is not maintainable without a
 >full-time contributor, we should pick our battles
 >
 >On Wed, Apr 14, 2021, 20:36 Mark Waite 
 >wrote:
 >
 >>
 >>
 >> On Wed, Apr 14, 2021 at 12:20 PM Daniel Beck  
 wrote:
 >>
 >>>
 >>> Since the last time we discussed this (and I created the JEP), we
 >added
 >>> deprecation warning support to Jenkins 2.246 and newer, which is
 >basically
 >>> designed for such a case. This makes JEP-7 much cleaner to
 >implement,
 >>> because we now have good ways to inform users about it.
 >>>
 >>> I'd start with a deprecation warning for ruby-runtime and all
 >dependent
 >>> plugins pointing to the JEP or this thread (or, if you want to write
 >it up,
 >>> a blog post), and if folks don't complain offer to take over
 >>> ruby-runtime maintainership in large enough numbers, we can suspend
 >a few
 >>> weeks later, followed by core cleanup. WDYT?
 >>>
 >>>
 >> +1 from me.
 >>
 >>
 >> --
 >> You received this message because you are subscribed to a topic in
 >the
 >> Google Groups "Jenkins Developers" group.
 >> To unsubscribe from this topic, visit
 >>
 >
 https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe
 .
 >> To unsubscribe from this group and all its topics, send an email to
 >> jenkinsci-de...@googlegroups.com.
 >> To view this discussion on the web visit
 >>
 >
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFpo1yfG81wQYMUYp9vq3wFP%2BE40zA5cyAuZLYAQF83JQ%40mail.gmail.com
 >>
 ><
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFpo1yfG81wQYMUYp9vq3wFP%2BE40zA5cyAuZLYAQF83JQ%40mail.gmail.com?utm_medium=email&utm_source=footer
 >
 >> .
 >>

 I believe there were plugins depending on it, that got me to have to 
 pick java8 explicitly on one system. I think gitlab-plugin might be it.

 Jim

 --
 Typos courtesy of K-9 Mail on my Android

 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Jenkins Developers" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/DCF391B5-3BB1-415C-BD17-10E0D2859FE6%40cos.ru
 .

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACEF8CtS5%2Bmd2WbipJSt0S9EHhp_ZJ96ZQ30KgTqXm4%3DEg%40mail.gmail.com
>>>  
>>>