Re: Chinese Localization SIG

If other languages contributors want to do a full localization work, such as Jenkins core, plugins, website and so on. We can consider building a 'Localization SIG'. But I don't get more feedback. On Thursday, August 16, 2018 at 2:24:15 AM UTC+8, Liam Newman wrote: > > I realize I'm late to

JEP Office Hours 2018-08-16

Hello all, At the last JEP office hours we discussed ways to comment on and ask questions about JEPs when there isn't a PR currently open. We looked at making edits to add comments or annotations. We also discussed a few other potential changes to the JEP process such as

Code review for making Managed-Scripts plugin pipeline compatible

Hi All, I have made the managed windows batch step of the managed scripts plugin pipeline compatible, but I don't like the way I did. I have posted the change to my repo here: https://github.com/mdkf/managed-scripts-plugin . My concerns are that the code I added to support pipeline is 90%

Re: Backporting for LTS 2.138.1 started

On Wed, Aug 15, 2018 at 2:32 PM Oliver Gondža wrote: > Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 IIUC all three are already fixed in 2.138 so need no backport, right? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Chinese Localization SIG

IMHO single-language SIGs are preferable. SIG is going to be coordinating the translation effort for Chinese, and I doubt the discussions will be relevant to other localization contributors (and vice versa). Obviously the discussions may be in Chinese if they are decoupled to a separate SIG. Which

Backporting for LTS 2.138.1 started

Backporting for the next LTS version has started. Note one of the seldom updated components, JNA, will be updated from version 4.2.1 to 4.5.2. Jenkins relies on it for OS specific operation Java Platform has/had no abstraction for, such as advanced file system operation, process manipulation,

Re: Chinese Localization SIG

I realize I'm late to this discussion, but could we make this the "Localization SIG". Having this be for one language alone seems a bit too narrow. Obviously, the core focus you'd like to work on is Chinese, but the work done there will likely overlap with Localization to other languages.

Re: tagged for adoption with both label as well as info in wiki. Does not show up in adopt-a-plugin list

> On 15. Aug 2018, at 17:20, Mike Caspar wrote: > > I've added labels as well as wiki page content to put plugin up for adoption. > > The list of plugins to be adopted doesn't show my plugin. I made the changes > about a month ago. > > Can someone please help put this up for adoption for

Re: Renaming Jenkins Essentials to 'Evergreen'

(replies inline) On Wed, 15 Aug 2018, Jesse Glick wrote: > On Tue, Aug 14, 2018 at 6:04 PM R. Tyler Croy wrote: > > The key aspect of it is _not_ the selection of > > plugins, but rather how those plugins get out there to users. > > That just means you are concealing one aspect behind another,

Re: Renaming Jenkins Essentials to 'Evergreen'

On Tue, Aug 14, 2018 at 6:04 PM R. Tyler Croy wrote: > The key aspect of it is _not_ the selection of > plugins, but rather how those plugins get out there to users. That just means you are concealing one aspect behind another, since the only plugins which would be distributed using the

Re: Hangouts Chat Plugin

Hi Baptiste, thanks for the note. I read the guidelines now and moved my code to Github: http://github.com/eickler/hangouts-chat. Cheers, André On Tuesday, 14 August 2018 17:56:20 UTC+2, Baptiste Mathus wrote: > > Hey folks, > > If, as you seem to, would like your work to get a bigger

tagged for adoption with both label as well as info in wiki. Does not show up in adopt-a-plugin list

Hi there, I've added labels as well as wiki page content to put plugin up for adoption. The list of plugins to be adopted doesn't show my plugin. I made the changes about a month ago. Can someone please help put this up for adoption for me. Thanks ironmq-notifier. -- You received this

Re: Renaming Jenkins Essentials to 'Evergreen'

I like the name change. I think I've seen both names lately, and I was confused which was what. Thanks for the clarification! On Tue, Aug 14, 2018 at 5:04 PM R. Tyler Croy wrote: > > I wanted to send an broader email to the dev list indicating that I will be > changing the name of what we have

Platform SIG: Meeting announcement (Aug 15, 2PM UTC)

Hi all, Today at 2PM UTC we will have a first meeting of the Jenkins Platform Special Interest Group . This is a new group focused on various platforms support: Java, Operating Systems, Architectures, Docker, Packaging, Web Containers, etc. Regarding the

Re: Bill of Materials

Thanks! On Tue, Aug 14, 2018, 17:38 R. Tyler Croy wrote: > (replies inline) > > On Tue, 07 Aug 2018, Oleg Nenashev wrote: > > > Hi Tyler, > > > > Thanks for the feedback! > > > > > > > I believe the only think which needs to be resolved which is likely > just an > > > obsolete part of the