Re: New LTS based on 2.107

2018-03-27 Thread Oliver Gondža
On 2018-03-27 09:09, Oleg Nenashev wrote: Hi Oliver, Do you plan to start the backporting thread for 2.107.2? There is one JEP-200 regression in the core, which potentially impacts all usages of Ant's DirectoryScanner in Remoting Calls: JENKINS-50237

Re: New LTS based on 2.107

2018-03-27 Thread Oleg Nenashev
Hi Oliver, Do you plan to start the backporting thread for 2.107.2? There is one JEP-200 regression in the core, which potentially impacts all usages of Ant's DirectoryScanner in Remoting Calls: JENKINS-50237 . Although we applied a

Re: New LTS based on 2.107

2018-02-26 Thread Oliver Gondža
I agree here to stick with the current choice. If we are still not sure using older baseline will avoid those regressions, I do not see a point in reconsidering. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: New LTS based on 2.107

2018-02-24 Thread Jesse Glick
On Sat, Feb 24, 2018 at 6:11 AM, Oleg Nenashev wrote: > Two regressions which are not fully triaged (JENKINS-49588, JENKINS-49630) > do seem as a major problem. Well they do look “major”, and they do seem to be regressions from something, but it is not at all obvious to

Re: New LTS based on 2.107

2018-02-24 Thread Oleg Nenashev
I do not buy this argument, because at the Governance meeting we explicitly agreed that we may fallback to 2.104 if "we find major problems" (meeting notes ). Two regressions which are not fully triaged

Re: New LTS based on 2.107

2018-02-23 Thread Jesse Glick
On Fri, Feb 23, 2018 at 12:17 PM, Oleg Nenashev wrote: > Since there is no > other related changes in 2.104+, I suspect XML 1.1 until proven otherwise. There are all sorts of unreported environmental issues which could also cause such problems. I do not think a vague

Re: New LTS based on 2.107

2018-02-23 Thread Oleg Nenashev
> > Since you're arguing for exclusion of the XML 1.1 change, could you > elaborate why JENKINS-49588 is related to XML 1.1 in your opinion, and what > the other issues are? According to the reporter

Re: New LTS based on 2.107

2018-02-23 Thread Daniel Beck
> On 23. Feb 2018, at 17:16, Oleg Nenashev wrote: > > • We have some regression reports probably related to XML 1.1 (JENKINS-49588, > fix has not been integrated yet + some other issues) > Since you're arguing for exclusion of the XML 1.1 change, could you elaborate

Re: New LTS based on 2.107

2018-02-23 Thread Oleg Nenashev
Some bits: - We have some regression reports probably related to XML 1.1 ( JENKINS-49588 , fix has not been integrated yet + some other issues) - We have an issue with Violations plugin breaking config UIs on new versions

Re: New LTS based on 2.107

2018-02-22 Thread Daniel Beck
> On 15. Feb 2018, at 09:26, Oliver Gondža wrote: > > As greed on Governance meeting, the next LTS line will be based on latest > weekly release. That means, there are no backports to be added for .1 > provided we do not discover something urgent that would cause us to