On Tue, Jul 19, 2022 at 5:31 AM Mark Waite <[email protected]> wrote:
> The preferred fix needs a new release of the commons-lang3-api plugin > <https://github.com/jenkinsci/commons-lang3-api-plugin/>. The current > maintainer has not responded to previous requests nor to the current > request > <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659> > 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 <https://github.com/jenkinsci/commons-lang3-api-plugin/> as > requested in the RPU pull request > <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659> > . > 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 <https://github.com/jenkinsci/configuration-as-code-plugin/pull/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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJDj1tMO9Sc04b3bar6v3MFXf10NnL555Wg%3DtWoEWCUpA%40mail.gmail.com.
