Heads-up: Jenkins 2.221 weekly release delay

Hi all, Just a quick update w.r.t. the weekly release status. The automatic release on the weekend did not go through on KK's release environment. Kohsuke suspects a power outage, and it is hard to fix it remotely. ETA for the fix - late Wed or Thursday in the US timezone. We can use the delay

Re: About - Simple Pull Request Plugin

Hi Oleg, Nice to meet you Vu Tuan. I have some doubts, may be you can help me understand things. - Why the name of the plugin is different ? Also It says it is about pull requests from various version controls. If this plugin will continue focusing on both, It will be good to separate them.

Re: Core Infrastructure Initiative (CII) compliance for the Jenkins core - status thread

Hi Oleg, Thanks for putting this together and establishing that baseline score! IMHO it is a great exercise to run through as proven by the issues you raised in the email. (Also nice to see the badge linked when I click on Jenkins on the CDF and CNCF

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

https://github.com/jenkins-infra/plugin-site/pull/130 for the plugin site update On Tuesday, February 18, 2020 at 10:05:40 AM UTC+1, Oleg Nenashev wrote: > > Yes, plugin site is something I will be doing (see the comments above). > The problem is rather with GitHub repositories and direct access

Core Infrastructure Initiative (CII) compliance for the Jenkins core - status thread

Hi all, This is a follow-up to the Community Bridge funding thread and to contributor summit discussions about CII. As discussed there, Linux Foundation expects all projects on Community Bridge to be also a part of the Core

Re: About - Simple Pull Request Plugin

Since you follow the existing plugin design, IMHO it would be better to just keep extending it. It is in alpha now, so there is no compatibility requirements. CC Vu Tuan who is the current maintainer BR, Oleg On Mon, Feb 17, 2020, 20:04 Aytunc Beken wrote: > Hi Oleg, > > Sorry for my late

Re: Proposal: Jenkins Core PR reviewers team

+1 to add Marky too. On Tue, Feb 18, 2020 at 9:59 AM Tim Jacomb wrote: > +1 from my side > > On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez < > fjfernan...@cloudbees.com> wrote: > >> Oleg, Marky, +1 from my side. Any help is always more than welcome! >> >> El domingo, 16 de febrero de

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

Yes, plugin site is something I will be doing (see the comments above). The problem is rather with GitHub repositories and direct access to them. In this case a badge could improve visibility of the adoption status. We could serve a badge from the plugin site for that, but IMHO it is a separate

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

The badge could be automatically added on the plugin site if one of the adopt topics is added to the GitHub repo? On Tue, 18 Feb 2020 at 08:01, Ivan Fernandez Calvo wrote: > Sure, the badge is something additional, > something that users can see when they go to the documentation, then they >

Re: Proposal: Jenkins Core PR reviewers team

+1 from my side On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez < fjfernan...@cloudbees.com> wrote: > Oleg, Marky, +1 from my side. Any help is always more than welcome! > > El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson > escribió: >> >> Thank you kindly Oleg,

Re: Proposal: Jenkins Core PR reviewers team

Oleg, Marky, +1 from my side. Any help is always more than welcome! El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson escribió: > > Thank you kindly Oleg, please do get well. Sending healing thoughts. > > On Feb 16, 2020, at 10:30 AM, Oleg Nenashev > wrote: > >  > Hi Marky. As

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

Sure, the badge is something additional, something that users can see when they go to the documentation, then they can decide if they want to use a plugin in adoption. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from