Re: PRs on jenkins-infra/repository-permissions-updater

2018-12-11 Thread Vacelet, Manuel
Hi Adrien, My PR got merged yesterday by Daniel Beck, thanks to him ! TBH, I did not know what to do (hence message here). The maintainers of the repo are not advertize in the Readme and it does not mention how to get in touch with "the team" either. Manuel On Tue, Dec 11, 2018 at 9:26 PM

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

2018-12-11 Thread Liam Newman
Oleg, I totally agree with how you described the SIG's relationship with channels - there to help, not to specifically own/control the channels. As to naming: 1. "Advocacy and Outreach" 2. "Outreach and Advocacy" 3. "Advocacy and Community Outreach" 4. "Community Outreach and

Re: PRs on jenkins-infra/repository-permissions-updater

2018-12-11 Thread Adrien Lecharpentier
Manuel, did you try to ping a current maintainer? Le lun. 10 déc. 2018 à 18:12, Manuel Vacelet a écrit : > Hi there, > > I got a PR on jenkins-infra/repository-permissions-updater pending since > 19 days without any info about why it's pending. > I saw in a previous message that there was some

Re: Java 11 Preview availability in Weekly releases. Status update (JEP-211)

2018-12-11 Thread Jesse Glick
On Tue, Dec 11, 2018 at 1:08 PM Oleg Nenashev wrote: > SUREFIRE-1588 effectively makes the recent PCT Docker image useless if > plugins are not updated to Plugin POM 3.28 or above You do not need to update plugin POMs; you can work around this with a `~/.m2/settings.xml` in the image. (Or

Re: Java 11 Preview availability in Weekly releases. Status update (JEP-211)

2018-12-11 Thread Oleg Nenashev
*Hi all,At the platform SIG meeting on Dec 04 we have signed-off the preview availability release for Java 11 support with Jenkins and decided to go forward with it (meeting notes ).

Re: Using Jenkins JIRA to record development priorities for a plugin?

2018-12-11 Thread Liam Newman
Awesome! On Tue, Dec 11, 2018 at 9:39 AM Mark Waite wrote: > I've taken one step further with the git plugin and the git client > plugin. I've created GitHub milestones > >- Git client plugin 3.0 > >- Git plugin 4.0

Re: Using Jenkins JIRA to record development priorities for a plugin?

2018-12-11 Thread Mark Waite
I've taken one step further with the git plugin and the git client plugin. I've created GitHub milestones - Git client plugin 3.0 - Git plugin 4.0 - Git client plugin

Re: Any idea how to release https://github.com/jenkinsci/xstream-fork

2018-12-11 Thread Oliver Gondža
On 11/12/2018 12.55, Oleg Nenashev wrote: `xstream` is what we use in Jenkins nowadays. `xstream-fork` has been created by Nicolas de Loof at some point, but this repository has never been updated to incorporate Jenkins-specific patches. And I am not sure whether it has passed the full test

Re: Any idea how to release https://github.com/jenkinsci/xstream-fork

2018-12-11 Thread nicolas de loof
As discussed already here , the *-fork repository have been created so that the jenkins flavours of those library are actual forks from upstreams, so we can better propose our

Re: Any idea how to release https://github.com/jenkinsci/xstream-fork

2018-12-11 Thread Oliver Gondža
On 11/12/2018 12.55, Oleg Nenashev wrote: `xstream` is what we use in Jenkins nowadays. `xstream-fork` has been created by Nicolas de Loof at some point, but this repository has never been updated to incorporate Jenkins-specific patches. And I am not sure whether it has passed the full test

Re: Any idea how to release https://github.com/jenkinsci/xstream-fork

2018-12-11 Thread Oleg Nenashev
`xstream` is what we use in Jenkins nowadays. `xstream-fork` has been created by Nicolas de Loof at some point, but this repository has never been updated to incorporate Jenkins-specific patches. And I am not sure whether it has passed the full test cycle. There is a splitbrain between the