Re: Re: [ANN] First call for 3.5.4 release

2018-06-08 Thread Stephen Connolly
2018 um 07:44 Uhr > > Von: "Stephen Connolly" > > An: "Maven Developers List" > > Betreff: Re: [ANN] First call for 3.5.4 release > > > > On Wed 16 May 2018 at 12:57, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > &

Re: Re: [ANN] First call for 3.5.4 release

2018-06-08 Thread Michael Osipov
> Gesendet: Freitag, 08. Juni 2018 um 07:44 Uhr > Von: "Stephen Connolly" > An: "Maven Developers List" > Betreff: Re: [ANN] First call for 3.5.4 release > > On Wed 16 May 2018 at 12:57, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote

Re: [ANN] First call for 3.5.4 release

2018-06-07 Thread Stephen Connolly
On Wed 16 May 2018 at 12:57, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Ok, MNG-6388 is a release blocker IMHO as it a regression introduced by > the upgrade of wagon in 3.5.3. > > So we need a wagon release with at least WAGON-496, WAGON-518, WAGON-513 > + WAGON-514 > > (WAGON-4

Re: [ANN] First call for 3.5.4 release

2018-05-20 Thread Michael Osipov
Am 2018-05-19 um 23:41 schrieb Stephen Connolly: MNG-6401 if somebody merges before wagon, +1 I have pushed two branches for it now. It passes all ITs locally. Jenkins fails for the TLS issue. Are we good to merge this one? On 19 May 2018 at 17:43, Robert Scholte wrote: What about [MNG-

Re: [ANN] First call for 3.5.4 release

2018-05-19 Thread Stephen Connolly
MNG-6401 if somebody merges before wagon, +1 On 19 May 2018 at 17:43, Robert Scholte wrote: > What about [MNG-6401] Cannot interpolate property in proxy port of > settings.xml ? > There's a PR and IT available > > Robert > > [1] https://issues.apache.org/jira/browse/MNG-6401 > > > > On Tue, 15 M

Re: [ANN] First call for 3.5.4 release

2018-05-19 Thread Robert Scholte
What about [MNG-6401] Cannot interpolate property in proxy port of settings.xml ? There's a PR and IT available Robert [1] https://issues.apache.org/jira/browse/MNG-6401 On Tue, 15 May 2018 13:35:47 +0200, Stephen Connolly wrote: As Hervé has merged the JAnsi fix, we are now unblocked

Re: [ANN] First call for 3.5.4 release

2018-05-16 Thread Michael Osipov
Am 2018-05-16 um 16:21 schrieb Robert Scholte: Maybe I missed something, but what does SCM have to do with Maven (core)? It's not part of the distribution, right? You don't miss anything, but Wagon uses SCM and I don't want to spin Wagon twice just for the SCM upgrade because my time on Maven

Re: [ANN] First call for 3.5.4 release

2018-05-16 Thread Robert Scholte
Maybe I missed something, but what does SCM have to do with Maven (core)? It's not part of the distribution, right? thanks, Robert On Tue, 15 May 2018 20:32:50 +0200, Michael Osipov wrote: Am 2018-05-15 um 13:35 schrieb Stephen Connolly: As Hervé has merged the JAnsi fix, we are now unbl

Re: [ANN] First call for 3.5.4 release

2018-05-16 Thread Stephen Connolly
Ok, MNG-6388 is a release blocker IMHO as it a regression introduced by the upgrade of wagon in 3.5.3. So we need a wagon release with at least WAGON-496, WAGON-518, WAGON-513 + WAGON-514 (WAGON-452 is optional from my PoV... up to whoever steps up as release manager for Wagon to decide the scope

Re: [ANN] First call for 3.5.4 release

2018-05-15 Thread Michael Osipov
Am 2018-05-15 um 21:44 schrieb Stephen Connolly: On Tue 15 May 2018 at 19:32, Michael Osipov wrote: Am 2018-05-15 um 13:35 schrieb Stephen Connolly: As Hervé has merged the JAnsi fix, we are now unblocked for cutting 3.5.4 I will give 72h for anyone to surface any issues they wish to claim

Re: [ANN] First call for 3.5.4 release

2018-05-15 Thread Michael Osipov
Am 2018-05-15 um 13:35 schrieb Stephen Connolly: As Hervé has merged the JAnsi fix, we are now unblocked for cutting 3.5.4 I will give 72h for anyone to surface any issues they wish to claim should be included in 3.5.4 and have not already been merged. As the person stepping up to be release ma

[ANN] First call for 3.5.4 release

2018-05-15 Thread Stephen Connolly
As Hervé has merged the JAnsi fix, we are now unblocked for cutting 3.5.4 I will give 72h for anyone to surface any issues they wish to claim should be included in 3.5.4 and have not already been merged. As the person stepping up to be release manager* for 3.5.4, I get to decide if: * your claim