Re: Adoption of the copyartifact-plugin which has been marked for adoption

+1 from me. Allan's recent pull request to the copyartifact plugin has been merged and released. The plugin is up for adoption and he's willing to adopt it. On Sunday, January 29, 2023 at 7:40:52 PM UTC-7 alla...@gmail.com wrote: >

Adoption of the copyartifact-plugin which has been marked for adoption

Hello, I would like to adopt the GitLab Plugin which has been marked for adoption. - Link of the plugin: https://github.com/jenkinsci/copyartifact-plugin - Status of the plugin: "For adoption" - My GitHub username/id: allancth - My

Renovatebot for cctray-xml-plugin

Hi! I see some previous emails on this list about using renovatebot for plugins. Is it possible to enable it? How do I enable renovatbot for https://github.com/jenkinsci/cctray-xml-plugin? - Rahul -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Adoption of the GitLab Plugin which has been marked for adoption

+1 from me (former maintainer), thanks for helping out! On Sun, Jan 29, 2023 at 6:26 AM Kris Stern wrote: > > Hi everyone, > > I would like to adopt the GitLab Plugin which has been marked for adoption. > > Link of the plugin: https://github.com/jenkinsci/gitlab-plugin > Status of the plugin:

Re: Removing inactive Core maintainers to reduce risk

On Sun, Jan 29, 2023 at 4:52 AM 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Thanks for the positive feedback! It was positive feedback about the intention, not necessarily the end result. > [To] widen the discussion before the act did not seem necessary. Especially > when such a

Re: [Event]: FOSDEM'23

Hi all, Just a quick update, we also want to have a Jenkins dinner on February 4th, 19:00 If you are interested in joining, please respond here: https://forms.gle/v1E6dF6cusWBXjJs9 Best regards, Oleg Nenashev On Thursday, January 5, 2023 at 8:43:48 PM UTC+1 alytong13 wrote: > Hi All, > >

Adoption of the GitLab Plugin which has been marked for adoption

Hi everyone, I would like to adopt the GitLab Plugin which has been marked for adoption. * Link of the plugin: https://github.com/jenkinsci/gitlab-plugin * Status of the plugin: "For adoption" * My GitHub username/id: krisstern * My Jenkins infrastructure account id: krisstern

Re: Next LTS baseline

Belated +1 On Wednesday, January 25, 2023 at 3:36:25 AM UTC+1 Mark Waite wrote: > +1 from me for 2.387. > > On Tuesday, January 24, 2023 at 2:30:47 AM UTC-7 mc.ca...@gmail.com wrote: > >> That would make a viable candidate. The response on the recent weekly >> releases has been overall very

Re: Removing inactive Core maintainers to reduce risk

I agree the cleanup is always useful, though it would be definitely nice to document explicit criteria in https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles . Not sure I even count as an active maintainer on my own these days, though my "sabbatical" was publicly

Re: Removing inactive Core maintainers to reduce risk

While I’m very much +1 for the change I think it should’ve been discussed on the mailing list publicly On Sun, 29 Jan 2023 at 13:52, 'wfoll...@cloudbees.com' via Jenkins Developers wrote: > Thanks for the positive feedback! > > > we decided > Decision was made between Damien and me. > It was

Re: Removing inactive Core maintainers to reduce risk

Thanks for the positive feedback! > we decided Decision was made between Damien and me. It was discussed with a few other people and as we got mainly just ultra positive response, widen the discussion before the act did not seem necessary. Especially when such a change can be reversed without