Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

FYI all. The Core PR got merged. Blog entry PR up for review https://github.com/jenkins-infra/jenkins.io/pull/4395 I think we should land this blog article asap, so people can start seeing this today to prepare for upcoming weekly. -- Baptiste Le mer. 2 juin 2021 à 01:00, Oleg Nenashev a

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Thanks a lot! > Then next is 6 years ago. Not holding my breath for these :-). Me neither. We need Basil's plugin EOL work to land > I'd like to declare the Digester PR ready-for-merge given the existing approvals. Fine with me. The weekly release is out, so it gives maintainers (if any) one

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Email thread pinging last maintainers' emails taken from git log just sent, see the other thread. Le mer. 2 juin 2021 à 00:05, Baptiste Mathus a écrit : > > > Le mar. 1 juin 2021 à 08:48, Oleg Nenashev a > écrit : > >> >> > I am not sure exactly sure what you mean by this, but I am certainly

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Le mar. 1 juin 2021 à 08:48, Oleg Nenashev a écrit : > > > I am not sure exactly sure what you mean by this, but I am certainly not > requesting nor expecting you to support any fallout of this PR. Our team > will obviously step up if something bad arises > > Sorry for confusion, I have no doubt

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

> I am not sure exactly sure what you mean by this, but I am certainly not requesting nor expecting you to support any fallout of this PR. Our team will obviously step up if something bad arises Sorry for confusion, I have no doubt that your team will provide good support for this change.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Dear Oleg, On Sun, May 30, 2021 at 11:55 AM Oleg Nenashev wrote: > I have commented about the plugins removal in another thread. In particular, you wrote: "From the list, I am particularly concerned about Code Coverage plugins which seemed to be actively used." You expressed concern about

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Le lun. 31 mai 2021 à 17:41, Oleg Nenashev a écrit : > > Just to make sure I get your point/stance: > > * you would agree we mark the current PR as ready-for-merge > > * [provided we enrich the JEP-231 with the following [?]] > > * to make things better for the future, you recommend we create a

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

I am against a digester API plugin as it is not really something that should be used and by making a plugin-api we make that somewhat offical. We took a quicker path of bumping the digester usage to support 3 than remove / replace it entirely. as there are only a few plugins using this I think

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

> Just to make sure I get your point/stance: > * you would agree we mark the current PR as ready-for-merge > * [provided we enrich the JEP-231 with the following [?]] > * to make things better for the future, you recommend we create a digester3-api plugin so these plugins can all be updated in

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Le dim. 30 mai 2021 à 20:55, Oleg Nenashev a écrit : > Hi all, > > I have commented about the plugins removal in another thread. I have a > question about creating a detached plugin for commons-digester: *" The > current plan causes plugins which depend on Jenkins to provide Digester to > fail

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Hi all, I have commented about the plugins removal in another thread. I have a question about creating a detached plugin for commons-digester: *" The current plan causes plugins which depend on Jenkins to provide Digester to fail unless they are updated. This could be mitigated by moving this

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

+1 from me -- 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

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Here's the PR submitting JEP for Digester Removal: https://github.com/jenkinsci/jep/pull/361 On Wed, May 5, 2021 at 10:37 AM Oleg Nenashev wrote: > Hi all. Please do not consider JEP as a huge overhead. As discussed in > another thread, we will be working on simplifying the process for >

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Hi all. Please do not consider JEP as a huge overhead. As discussed in another thread, we will be working on simplifying the process for contributors. The process is not meant to be an obstacle, and I plan to keep simplifying it where possible. And, to everyone, please be kind. All of us share

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Le mer. 5 mai 2021 à 19:08, Jesse Glick a écrit : > On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev > wrote: > >> What about a quick JEP? >> > > The rule of thumb is that if you are not sure if a JEP might be > needed…file a JEP. It is how we document any decision that might be > controversial or

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

On Tue, May 4, 2021 at 10:58 PM Oleg Nenashev wrote: > What about a quick JEP? > The rule of thumb is that if you are not sure if a JEP might be needed…file a JEP. It is how we document any decision that might be controversial or require explanation or context. Certainly any deliberate

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Exactly what Liam said. I did call out this very page about "compatibility matters" on my first mail in this thread. I think we *are* being extremely careful. We even filed PRs on plugins that the Jenkins Project does not serve anymore and/or plugins abandoned since close to 10 years. Le mer. 5

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Daniel, >From that link: > This is not to say we don’t ever remove anything, but we do it very > carefully. > We are being careful. I think creating a JEP, even a mostly retrospective one, is worth doing. If nothing else we should do so because of concerns like those voiced by Daniel. I will

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

> On 5. May 2021, at 09:41, Manuel Ramón León Jiménez > wrote: > > I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in for > anything to avoid us dealing with the same problems in the future. We need to > modernize Jenkins in many aspects and those old / unmaintained

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in for anything to avoid us dealing with the same problems in the future. We need to modernize Jenkins in many aspects and those old / unmaintained plugins are an obstacle and a waste of effort. Something like put for adoption

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

What about a quick JEP? We are working on removing obstacles in the process, an a test for the new process would be great On Wed, May 5, 2021, 01:16 Basil Crow wrote: > On Tue, May 4, 2021 at 2:02 PM Baptiste Mathus wrote: > > So the big question is: what do we do? > > > > I personally think

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

On Tue, May 4, 2021 at 2:02 PM Baptiste Mathus wrote: > So the big question is: what do we do? > > I personally think we should NOT make these PRs land if no maintainer steps > up. > In other words, once we merge and release the Core PR, these plugins will > likely just fail loading on newer

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

On Tue, May 4, 2021 at 5:02 PM Baptiste Mathus wrote: > >- cvs still being reported as installed 40k times... > > Of course most of those installations are unused; it is a detached plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Hi all, so our team landed all 23 PRs needed to adapt the identified impacted plugins in the ecosystem. The thing is: in those PRs, many plugins are just abandoned, some since up to 9 years. The detailed status table is available on the PR itself: https://github.com/jenkinsci/jenkins/pull/5320 I

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Hi Baptiste, Thanks a lot for this work! Commons Digester is definitely a legacy that we should rather remove from Jenkins. It should be perfectly fine as long as we provide an upgrade path in plugins, timely deprecate and announce the removal. We're doing pretty much the same process for Ruby

[Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

Hi all, I was considering just posting a link in the plugins EOL thread, but thought I'd fork to keep the other thread focused. (and not end up stealing it). We are currently working on *removing* commons-digester:2.1