Here's the patch for 10.10 that we should cherry-pick:

commit 8adb36e3f72b575dea53013e7e790cb6c7957ae0
Author: Benjamin Mahler <bmah...@twitter.com>
Date:   Tue Nov 11 15:11:32 2014 -0800
    Added missing ZooKeeper patch file to the Makefile.

I'll mark https://issues.apache.org/jira/browse/MESOS-1797 for 0.21.0.

On Tue, Nov 11, 2014 at 3:08 PM, Benjamin Mahler <benjamin.mah...@gmail.com>
wrote:

> +till
>
> FYI for Mac OS X 10.10.
>
> Had to install subversion and apr:
>
> $ brew tap homebrew/versions
> $ brew tap homebrew/apache
> $ brew install subversion apr
>
> There is a flaky test in libprocess:
>
> [ RUN      ] IO.Write
> make[5]: *** [check-local] Broken pipe: 13
>
> Filed: https://issues.apache.org/jira/browse/MESOS-2079
>
> Then I couldn't get ZooKeeper to compile:
> https://gist.github.com/bmahler/71822e25fcb195d8df4b
>
> Re-opened https://issues.apache.org/jira/browse/MESOS-1797 to get the
> .patch file included in the Makefile.
>
>
> On Tue, Nov 11, 2014 at 1:59 PM, Niklas Nielsen <nik...@mesosphere.io>
> wrote:
>
>> +1 Mac OS X 10.9.5 and Ubuntu trusty
>>
>> Niklas
>>
>> On 11 November 2014 10:11, Vinod Kone <vinodk...@gmail.com> wrote:
>>
>>> +1
>>>
>>> Successfully deployed to our test clusters.
>>>
>>> On Mon, Nov 10, 2014 at 2:23 PM, Ian Downes <idow...@twitter.com.invalid
>>> >
>>> wrote:
>>>
>>> > Hi all,
>>> >
>>> > Please vote on releasing the following candidate as Apache Mesos
>>> 0.21.0.
>>> >
>>> > 0.21.0-rc2 added the following commits to 0.21.0-rc1:
>>> > $ git cherry -v 0.21.0-rc1
>>> > + cf2e056a2168cc3ce40d6669840bebb1a8cf166a Fixed Authenticator SASL
>>> > auxiliary memory access.
>>> > + 5aded98535cf5152050750b63a3adb5a32ab8bcb Added slave metrics for
>>> total
>>> > and used resources.
>>> > + 8f84af39e49701a1152855fa24c6eefb3167f0f2 Fixed invalid characters in
>>> > external-containerizer.md
>>> > + 4feb4f2e68db85c3aaa7f28c909173b23b2cbbeb Added check for apr and svn
>>> > headers besides libraries
>>> > + fba2dc4c7d923be143f40c9758030675bb8ee6a2 Added check for apr and svn
>>> > headers besides libraries in 3rdparty
>>> > + fd6cd057ca3dd1b5e944820e9da743725c91f5f2 Always recover 'completed'
>>> in
>>> > RunState.
>>> > + 42431c362f87408b3822e2b1e2736eaec5f458d7 Add to 0.21.0 CHANGELOG.
>>> >
>>> >
>>> > 0.21.0 includes the following:
>>> >
>>> >
>>> --------------------------------------------------------------------------------
>>> > State reconciliation for frameworks
>>> > Support for Mesos modules
>>> > Task status now includes source and reason
>>> > A shared filesystem isolator
>>> > A pid namespace isolator
>>> >
>>> > 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.21.0-rc2
>>> >
>>> >
>>> --------------------------------------------------------------------------------
>>> >
>>> > The candidate for Mesos 0.21.0 release is available at:
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.21.0-rc2/mesos-0.21.0.tar.gz
>>> >
>>> > The tag to be voted on is 0.21.0-rc2:
>>> >
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.21.0-rc2
>>> >
>>> > The MD5 checksum of the tarball can be found at:
>>> >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.21.0-rc2/mesos-0.21.0.tar.gz.md5
>>> >
>>> > The signature of the tarball can be found at:
>>> >
>>> >
>>> https://dist.apache.org/repos/dist/dev/mesos/0.21.0-rc2/mesos-0.21.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-1040
>>> >
>>> > Please vote on releasing this package as Apache Mesos 0.21.0!
>>> >
>>> > The vote is open until Thu Nov 13 14:18:18 PST 2014 and passes if a
>>> > majority of at least 3 +1 PMC votes are cast.
>>> >
>>> > [ ] +1 Release this package as Apache Mesos 0.21.0
>>> > [ ] -1 Do not release this package because ...
>>> >
>>> > Thanks,
>>> >
>>> > Ian
>>> >
>>>
>>
>>
>

Reply via email to