Re: Plugin end-of-life (EOL) policy

To be honest, I was a bit taken by surprise at the intensity of the discussions regarding this topic. I was expecting that we could all agree on some basic criteria, publish a simple statement to that effect on jenkins.io, and refer to that policy as necessary while doing work on new features or

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

[Digester/ACTION REQUIRED] Release needed for plugins: teamconcert, vs-code-metrics, BlameSubversion, javatest-report, vss, genexus, synergy, config-rotator, harvest, cmvc to avoid them to break

Hi, (in CC the Jenkins developers ML) You're receiving this email because your email appeared in "git log" for one of the Jenkins plugins listed in the email subject. This plugin is *going to start breaking with next Jenkins weekly without an action*. If you still consider yourself a maintainer

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: [Digester] Adopt plugins emma & cloverphp

I am definitely +1 for adoption though the pull requests were merged too early IMHO. We usually have a 2-weeks response timeout, and we are yet to approve the Plugin EOL policy from Basil. On Monday, May 31, 2021 at 11:24:24 PM UTC+2 Baptiste Mathus wrote: > PR >

Re: I would like to become committer/maintainer on a plugin

Added Sven Schönung, the current Calendar View Plugin maintainer, to Cc. If we get approval for the plugin adoption, we can transfer the permissions quickly On Tue, Jun 1, 2021 at 7:26 PM Oleg Nenashev wrote: > Hi Roland, > > Thanks for your contributions! Indeed it does not look that the

Re: I would like to become committer/maintainer on a plugin

Hi Roland, Thanks for your contributions! Indeed it does not look that the Calendar View plugin is actively maintained. It has not been put for adoption either, so we will need to ping the maintainer and wait for a 2 weeks timeout if no response. I will help with that Best regards, Oleg

Looking for information about software production process

Hi everyone, other three students and I are working on a project/report for our software engineering course of University of Padova (Italy). We had to choose an open source project to analyze under some aspects like software production process and code metrics (in particular CK, LLOC, CC). We

Re: Jenkins 3.x

Hi all, Just a quick update for this and the related discussions: - As we discussed at the governance meeting, the Jenkins 3 discussions were scheduled to the Jenkins Contributor Summit on June 25th . My plan

Re: Where to implement GitLab Branch Source MR Naming change

Thanks for the pointer! I came up with theese changes to implement the `Job.displayName` variant: https://github.com/jenkinsci/branch-api-plugin/pull/254 The tests are really unhappy about my call to `getAction` =( However I only consider this a POC at this point and would like to get

Re: [jenkinsci-board] Proposal: Jenkins funding page on LFX Crowdfunding

> Am 01.06.2021 um 07:45 schrieb Oleg Nenashev : > > Thanks to Ulli for the feedback and for offering help! Restored the dev list > in CC. > > Seems that the bureaucracy is starting to increase in several areas of > Jenkins now, but maybe this is a very subjective view. (But I am not a fan

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.