Re: Grant timja immediate permissions to commons-lang3-api plugin

[Tim Jacomb]

I've temporarily reverted it
https://github.com/jenkinsci/configuration-as-code-plugin/releases/tag/1511.vb_f985b_894e40

Once the plugin is sorted we will re-add it to JCasC. We have fairly
frequent pain in conflicts from both commons-text and commons-lang3 and
this was an attempt to put an end to that.

On Tue, 19 Jul 2022 at 07:42, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
> On Tue, Jul 19, 2022 at 5:31 AM Mark Waite 
> wrote:
>
>> The preferred fix needs a new release of the commons-lang3-api plugin
>> .  The current
>> maintainer has not responded to previous requests nor to the current
>> request
>> 
>> that asks to grant Tim Jacomb permission to maintain the plugin.
>>
>> The usual process would require a 2 week wait for the adoption request to
>> "time out".  I propose an exception in this case based on the need to
>> deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins
>> release officer, a long-standing contributor to the Jenkins project, and a
>> strong contributor.
>>
>> I propose that Tim be granted permission immediately to maintain the  
>> commons-lang3-api
>> plugin  as
>> requested in the RPU pull request
>> 
>> .
>>
>
> As I wrote in the RPU PR, the easy fix without plugin governance
> challenges is to remove the ill-advised dependency from
> configuration-as-code, reverting
> jenkinsci/configuration-as-code-plugin#1979
>  [of
> which Tim is already a maintainer]. It seems unnecessary to go over
> maintainers' heads while that's an option. While this is the only plugin
> with the dependency, there's no benefit in conflict prevention anyway, and
> the PR provides no justification.
>
> --
> 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/CAMo7PtJDj1tMO9Sc04b3bar6v3MFXf10NnL555Wg%3DtWoEWCUpA%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/CAH-3Bicz2rTT0TJZ7G_EcNwsonP3P5PAmuU9DTTzagMV592agA%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

['Daniel Beck' via Jenkins Developers]

On Tue, Jul 19, 2022 at 5:31 AM Mark Waite 
wrote:

> The preferred fix needs a new release of the commons-lang3-api plugin
> .  The current
> maintainer has not responded to previous requests nor to the current
> request
> 
> that asks to grant Tim Jacomb permission to maintain the plugin.
>
> The usual process would require a 2 week wait for the adoption request to
> "time out".  I propose an exception in this case based on the need to
> deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins
> release officer, a long-standing contributor to the Jenkins project, and a
> strong contributor.
>
> I propose that Tim be granted permission immediately to maintain the  
> commons-lang3-api
> plugin  as
> requested in the RPU pull request
> 
> .
>

As I wrote in the RPU PR, the easy fix without plugin governance challenges
is to remove the ill-advised dependency from configuration-as-code,
reverting jenkinsci/configuration-as-code-plugin#1979
 [of
which Tim is already a maintainer]. It seems unnecessary to go over
maintainers' heads while that's an option. While this is the only plugin
with the dependency, there's no benefit in conflict prevention anyway, and
the PR provides no justification.

-- 
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/CAMo7PtJDj1tMO9Sc04b3bar6v3MFXf10NnL555Wg%3DtWoEWCUpA%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

[Raihaan Shouhell]

+1

This is break is quite severe

Cheers,
Raihaan

On Tue, Jul 19, 2022, 1:20 PM Basil Crow  wrote:

> +UINT64_MAX
>
> On Mon, Jul 18, 2022 at 8:31 PM Mark Waite 
> wrote:
>
>> A release of the Apache mina API plugins (core and common) have exposed a
>> cyclic dependency between the mina plugins, configuration as code, and
>> other plugins.  Details are into from
>> https://issues.jenkins.io/browse/JENKINS-69034
>>  .
>> A workaround is available, but a fix would be much better for users than
>> the workaround.
>>
>> The preferred fix needs a new release of the commons-lang3-api plugin
>> .  The current
>> maintainer has not responded to previous requests nor to the current
>> request
>> 
>> that asks to grant Tim Jacomb permission to maintain the plugin.
>>
>> The usual process would require a 2 week wait for the adoption request to
>> "time out".  I propose an exception in this case based on the need to
>> deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins
>> release officer, a long-standing contributor to the Jenkins project, and a
>> strong contributor.
>>
>> I propose that Tim be granted permission immediately to maintain the  
>> commons-lang3-api
>> plugin  as
>> requested in the RPU pull request
>> 
>> .
>>
>> Mark Waite
>>
>> --
>> 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/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%40googlegroups.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/CAFwNDjrbhAkTTe48on0nY105HbZJCrOx8Yt5MS%3Ddf%3D0sL1Pm4A%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/CAFoxvgw2%2Bdk9UjUOits7hvF4M-qK_H5RLXJHqaEpjwmASa3VLA%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

[Basil Crow]

+UINT64_MAX

On Mon, Jul 18, 2022 at 8:31 PM Mark Waite 
wrote:

> A release of the Apache mina API plugins (core and common) have exposed a
> cyclic dependency between the mina plugins, configuration as code, and
> other plugins.  Details are into from
> https://issues.jenkins.io/browse/JENKINS-69034
>  .
> A workaround is available, but a fix would be much better for users than
> the workaround.
>
> The preferred fix needs a new release of the commons-lang3-api plugin
> .  The current
> maintainer has not responded to previous requests nor to the current
> request
> 
> that asks to grant Tim Jacomb permission to maintain the plugin.
>
> The usual process would require a 2 week wait for the adoption request to
> "time out".  I propose an exception in this case based on the need to
> deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins
> release officer, a long-standing contributor to the Jenkins project, and a
> strong contributor.
>
> I propose that Tim be granted permission immediately to maintain the  
> commons-lang3-api
> plugin  as
> requested in the RPU pull request
> 
> .
>
> Mark Waite
>
> --
> 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/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%40googlegroups.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/CAFwNDjrbhAkTTe48on0nY105HbZJCrOx8Yt5MS%3Ddf%3D0sL1Pm4A%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

['Gavin Mogan' via Jenkins Developers]

your first link doesn't actually goto
https://issues.jenkins.io/browse/JENKINS-69034

I'm very much +1 with the mess of that sshd plugin has caused all day.
I've been redirecting threads and issues and stuff.

Gavin

On Mon, Jul 18, 2022 at 8:31 PM Mark Waite  wrote:
>
> A release of the Apache mina API plugins (core and common) have exposed a 
> cyclic dependency between the mina plugins, configuration as code, and other 
> plugins.  Details are into from 
> https://issues.jenkins.io/browse/JENKINS-69034 .  A workaround is available, 
> but a fix would be much better for users than the workaround.
>
> The preferred fix needs a new release of the commons-lang3-api plugin.  The 
> current maintainer has not responded to previous requests nor to the current 
> request that asks to grant Tim Jacomb permission to maintain the plugin.
>
> The usual process would require a 2 week wait for the adoption request to 
> "time out".  I propose an exception in this case based on the need to deliver 
> a new release of the commons-lang3-api-plugin.  Tim is the Jenkins release 
> officer, a long-standing contributor to the Jenkins project, and a strong 
> contributor.
>
> I propose that Tim be granted permission immediately to maintain the  
> commons-lang3-api plugin as requested in the RPU pull request.
>
> Mark Waite
>
> --
> 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/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%40googlegroups.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_Dusji%2B10cuJwT6E78tOSS4bjTg9hQg1F8werY6e3599AVw%40mail.gmail.com.

Grant timja immediate permissions to commons-lang3-api plugin

[Mark Waite]

A release of the Apache mina API plugins (core and common) have exposed a 
cyclic dependency between the mina plugins, configuration as code, and 
other plugins.  Details are into from 
https://issues.jenkins.io/browse/JENKINS-69034 
 .  
A workaround is available, but a fix would be much better for users than 
the workaround.

The preferred fix needs a new release of the commons-lang3-api plugin 
.  The current 
maintainer has not responded to previous requests nor to the current request 
 
that asks to grant Tim Jacomb permission to maintain the plugin.

The usual process would require a 2 week wait for the adoption request to 
"time out".  I propose an exception in this case based on the need to 
deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins 
release officer, a long-standing contributor to the Jenkins project, and a 
strong contributor.

I propose that Tim be granted permission immediately to maintain the  
commons-lang3-api 
plugin  as 
requested in the RPU pull request 
.

Mark Waite

-- 
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/d7ca0365-4600-4097-8dd4-d3c9f93e5327n%40googlegroups.com.