[RESULT][VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-18 Thread Kapil Arya
Hi all, The vote for Mesos 1.4.0 (rc5) has passed with the following votes. +1 (Binding) -- Vinod Kone Kapil arya Anand Mazumdar There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.0 It is recommended to use

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-18 Thread Anand Mazumdar
+1 (binding) make check passed on Ubuntu 16.04 -anand On Fri, Sep 15, 2017 at 2:12 PM, Kapil Arya wrote: > +1 (binding) > > Internal CI with Centos 6/7, Fedora 23, Debian 8, and Ubuntu 12/14/16. > > On Fri, Sep 15, 2017 at 5:08 PM, Vinod Kone wrote:

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-15 Thread Kapil Arya
+1 (binding) Internal CI with Centos 6/7, Fedora 23, Debian 8, and Ubuntu 12/14/16. On Fri, Sep 15, 2017 at 5:08 PM, Vinod Kone wrote: > Ok. Looks like a test issue per https://reviews.apache.org/r/60467/ > > +1(binding) > > On Fri, Sep 15, 2017 at 12:16 PM, Michael Park

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-15 Thread Vinod Kone
Ok. Looks like a test issue per https://reviews.apache.org/r/60467/ +1(binding) On Fri, Sep 15, 2017 at 12:16 PM, Michael Park wrote: > Vinod, regarding MESOS-7729 > : > > I found MESOS-6345

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-15 Thread Michael Park
Vinod, regarding MESOS-7729 : I found MESOS-6345 related to persistent volume framework, which leads me to believe that this is not new. Thanks, MPark On Tue, Sep 12, 2017 at 12:01 PM Vinod

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-12 Thread Vinod Kone
Tested this on ASF CI. Saw 3 flaky tests. https://issues.apache.org/jira/browse/MESOS-7729 https://issues.apache.org/jira/browse/MESOS-7971 https://issues.apache.org/jira/browse/MESOS-7972 The first one was a known (since 1.4.0) flaky test

[VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-09 Thread Kapil Arya
Hi all, [NOTE: Starting with this RC candidate, we will not be "releasing" RC jar files in the Maven release channel. This prevents polluting of the Maven repositories with numerous RC tags. As before, you can continue to test the release candidate using the Maven staging repository provided