Re: Moving forward on 3.5.0

2017-01-10 Thread Stephen Connolly
Yes that is my current working theory. It fails and passes at random on I think the Windows nodes On Tue 10 Jan 2017 at 23:36, Guillaume Boué wrote: > Yes, was following as well. Looks like the test > > MavenITmng3599useHttpProxyForWebDAVTest > > < > https://builds.apache.org/job/maven-jenkinsf

Re: Moving forward on 3.5.0

2017-01-10 Thread Guillaume Boué
Yes, was following as well. Looks like the test MavenITmng3599useHttpProxyForWebDAVTest didn't pass. Weird because it passed

Re: Moving forward on 3.5.0

2017-01-10 Thread Stephen Connolly
https://builds.apache.org/job/maven-jenkinsfile/job/MNG-6117/ build in progress... let's see how it does On 10 January 2017 at 22:01, Guillaume Boué wrote: > I created the branch for MNG-6117 with commit: > https://git1-us-west.apache.org/repos/asf?p=maven.git;a=comm > it;h=bd98ae6a3de8d443f5b3d

Re: Moving forward on 3.5.0

2017-01-10 Thread Guillaume Boué
I created the branch for MNG-6117 with commit: https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=bd98ae6a3de8d443f5b3d2f895f2348c2912ae05 I will merge the branch into master on Monday the 16th if there are no objections. Thanks, Guillaume Le 09/01/2017 à 12:06, Stephen Connoll

Moving forward on 3.5.0

2017-01-09 Thread Stephen Connolly
OK, I have updated the versions in JIRA. Issues which have been agreed in the Big Scrub thread as being accepted for 3.5.0 are all now marked with FixVersion = 3.5.0 Issues which have been proposed for 3.5.0 but have not yet been agreed for 3.5.0 are now all marked with FixVersion = 3.5.0-candida