Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3C8E61879D for ; Thu, 10 Dec 2015 15:06:58 +0000 (UTC) Received: (qmail 8090 invoked by uid 500); 10 Dec 2015 15:06:57 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 8027 invoked by uid 500); 10 Dec 2015 15:06:57 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 8017 invoked by uid 99); 10 Dec 2015 15:06:57 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 15:06:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4030CCA230 for ; Thu, 10 Dec 2015 15:06:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.901 X-Spam-Level: ** X-Spam-Status: No, score=2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=mesosphere.io Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id s091w7aSQ13J for ; Thu, 10 Dec 2015 15:06:44 +0000 (UTC) Received: from mail-ig0-f198.google.com (mail-ig0-f198.google.com [209.85.213.198]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 98DBC429D0 for ; Thu, 10 Dec 2015 15:06:44 +0000 (UTC) Received: by igcph11 with SMTP id ph11so47200655igc.3 for ; Thu, 10 Dec 2015 07:06:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mesosphere.io; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wyd3cReLHkaXEe+7EdqGjz+AJOWNNyecc4fW6ZfjFSg=; b=cYoF6nQrltIRS+AvZHRHRZ0wtl51GmlxFBX7nwrMG+qXGW3B/5VlTP8efLIHuzBKje MT8D1Z36iuYgDL9V1iTYWUaGE5rufFqvWNG4yfkaoNtLVK9z+/6NxGzAb0qkRlg6Sfmw A32sB6hOTg1v+hMyiW++T1UX8aPrISOg2EZ6I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wyd3cReLHkaXEe+7EdqGjz+AJOWNNyecc4fW6ZfjFSg=; b=YmR+zXVKJa9EbHjAreZZqUKOAlsOYvRwWXjNua+NhFZHfXVWNVoOSgxZ16N32DfB/s +a9SkBbP2tKk54ybf7kxRCDancXrWOQm25RNAOjgqvYY+gWnHi24mPmy0W3sa4ZSaMPq qk5eaoZhBNzvziaSiBRQDr4jH7yxmoljvUmZPFhbKD+OVCHtQUU7Qx7B84aa3UpZ5p5d qmZyRjLT8HW1ld5wEFgC2ALmCGeGlIAX1fDX36+eUhW2ewkBVUp87ca+xAiUO5x2funv 77TV3rD7SUAw3dSg/c+ZJGOnVzFOS/asGPRAURlnRxZJZoOcBa4s2p1/ngh/BOtvK+bX fBXA== X-Gm-Message-State: ALoCoQlALRwNjIWOOLHox3mxEt8KdlTubD2HwSCRSr+CqS74DAL//5ZqAT+BRC5bmS9HY/qZELaEadyp2Mnilk+IaCOUpiplBwPQU3hqcb+ryWUk7XstI5k= MIME-Version: 1.0 X-Received: by 10.60.95.34 with SMTP id dh2mr161920oeb.28.1449760004151; Thu, 10 Dec 2015 07:06:44 -0800 (PST) Received: by 10.182.22.232 with HTTP; Thu, 10 Dec 2015 07:06:44 -0800 (PST) In-Reply-To: <4FC36A6B-6D69-4AE0-B0F5-55F7D7EDB031@mesosphere.io> References: <129A9398-F394-4C55-A27C-0D9FB1E2DB21@me.com> <4FC36A6B-6D69-4AE0-B0F5-55F7D7EDB031@mesosphere.io> Date: Thu, 10 Dec 2015 16:06:44 +0100 Message-ID: Subject: Re: [VOTE] Release Apache Mesos 0.26.0 (rc4) From: Jan Schlicht To: user@mesos.apache.org Cc: dev Content-Type: multipart/alternative; boundary=089e011773410eb50c05268c8e36 --089e011773410eb50c05268c8e36 Content-Type: text/plain; charset=UTF-8 +1 (non-binding) Tested on OS X, Fedora 23, and CentOS 7.1 with and without SSL. `sudo ./bin/mesos-tests.sh` was fine, apart from known (non blocker) issues. On Thu, Dec 10, 2015 at 1:37 PM, Bernd Mathiske wrote: > I think that whereas this would clearly be a desirable bug fix to have, it > is not a blocker: > - Not a regression. This problem has been around for a long time, since > 0.20 AFAIK. > - There is a simple workaround. > > Bernd > > On Dec 10, 2015, at 3:05 AM, Benjamin Mahler > wrote: > > I'd really like to pull in the fix for: > https://issues.apache.org/jira/browse/MESOS-4106 > > This has been a long standing bug that makes the health checking not > function correctly some of the time. While it is rare in CI, it appeared in > a colleague's cluster for about a third of the tasks he was launching to > demonstrate how he ran into this. The fix is trivial and is in review. > > Thoughts? > > On Tue, Dec 8, 2015 at 7:01 AM, Bernd Mathiske > wrote: > >> +1 (binding) >> >> Ran make check, make distcheck, sudo bin/mesos-tests.sh, with SSL enabled >> and without on: Ubuntu 12.04, CentOS 7.1. >> >> Had 4 test failures with CentOS 7.1 for each configuration variant. All >> of the failed tests are known to be flaky, they have MESOS tickets, and >> they have been investigated and are deemed non-blockers. >> >> Bernd >> >> > On Dec 8, 2015, at 4:59 AM, Till Toenshoff wrote: >> > >> > Hi friends, >> > >> > we had noticed some discrepancies between the V0 API and the V1 API, >> > hence we had to create a new release candidate even after the voting of >> > 0.26.0-rc3 had officially ended. Sorry for that! >> > >> > Please vote on releasing the following candidate as Apache Mesos 0.26.0. >> > >> > The CHANGELOG for the release is available at: >> > >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.26.0-rc4 >> > >> -------------------------------------------------------------------------------- >> > >> > The candidate for Mesos 0.26.0 release is available at: >> > >> https://dist.apache.org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz >> > >> > The tag to be voted on is 0.26.0-rc4: >> > >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.0-rc4 >> > >> > The MD5 checksum of the tarball can be found at: >> > >> https://dist.apache.org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz.md5 >> > >> > The signature of the tarball can be found at: >> > >> https://dist.apache.org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz.asc >> > >> > The PGP key used to sign the release is here: >> > https://dist.apache.org/repos/dist/release/mesos/KEYS >> > >> > The JAR is up in Maven in a staging repository here: >> > https://repository.apache.org/content/repositories/orgapachemesos-1093 >> > >> > Please vote on releasing this package as Apache Mesos 0.26.0! >> > >> > The vote is open until Fri Dec 11 04:50:51 CET 2015 and passes if a >> majority of at least 3 +1 PMC votes are cast. >> > >> > [ ] +1 Release this package as Apache Mesos 0.26.0 >> > [ ] -1 Do not release this package because ... >> > >> > Thanks, >> > Bernd & Till >> > >> >> > > -- *Jan Schlicht* Distributed Systems Engineer, Mesosphere --089e011773410eb50c05268c8e36 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
+1 (non-binding)

Tested on OS X, Fedora= 23, and CentOS 7.1 with and without SSL.
`sudo ./bin/mesos-tests= .sh` was fine, apart from known (non blocker) issues.

On Thu, Dec 10, 2015 at 1:3= 7 PM, Bernd Mathiske <bernd@mesosphere.io> wrote:
I think that = whereas this would clearly be a desirable bug fix to have, it is not a bloc= ker:
- Not a regression. This problem has been around for a long time, = since 0.20 AFAIK.
- There is a simple workaround.

Bernd
=

= On Dec 10, 2015, at 3:05 AM, Benjamin Mahler <benjamin.mahler@gmail.com> wrot= e:

I'd really like to pull in the fix fo= r:<= div>
This has been a long standing bug that makes the health = checking not function correctly some of the time. While it is rare in CI, i= t appeared in a colleague's cluster for about a third of the tasks he w= as launching to demonstrate how he ran into this. The fix is trivial and is= in review.

Thoughts?

On Tue, Dec 8, 2015 at 7:01 AM, Be= rnd Mathiske <bernd@mesosphere.io> wrote:
+1 (binding)

Ran make check, make distcheck, sudo bin/mesos-tests.sh, with SSL enabled a= nd without on: Ubuntu 12.04, CentOS 7.1.

Had 4 test failures with CentOS 7.1 for each configuration variant. All of = the failed tests are known to be flaky, they have MESOS tickets, and they h= ave been investigated and are deemed non-blockers.

Bernd

> On Dec 8, 2015, at 4:59 AM, Till Toenshoff <toenshoff@me.com> wrote:
>
> Hi friends,
>
> we had noticed some discrepancies between the V0 API and the V1 API, > hence we had to create a new release candidate even after the voting o= f
> 0.26.0-rc3 had officially ended. Sorry for that!
>
> Please vote on releasing the following candidate as Apache Mesos 0.26.= 0.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=3Dmesos.git;a=3Dblob_plain;f= =3DCHANGELOG;hb=3D0.26.0-rc4
> ----------------------------------------------------------------------= ----------
>
> The candidate for Mesos 0.26.0 release is available at:
> https://dist.apache.= org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz
>
> The tag to be voted on is 0.26.0-rc4:
> https://git-wip-= us.apache.org/repos/asf?p=3Dmesos.git;a=3Dcommit;h=3D0.26.0-rc4
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apa= che.org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apa= che.org/repos/dist/dev/mesos/0.26.0-rc4/mesos-0.26.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/releas= e/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache= .org/content/repositories/orgapachemesos-1093
>
> Please vote on releasing this package as Apache Mesos 0.26.0!
>
> The vote is open until Fri Dec 11 04:50:51 CET 2015 and passes if a ma= jority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.26.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Bernd & Till
>





--
Jan Schlicht
Distributed Systems Engineer, Mesosphere
<= /div>
--089e011773410eb50c05268c8e36--