Re: [VOTE] Release Apache Mesos 1.0.4 (rc1)

[Adam Bordelon]

-0, wish we could include the fix for
https://issues.apache.org/jira/browse/MESOS-7265 in 1.0.4, but I won't hold
the release for it.

On Mon, Apr 17, 2017 at 3:44 PM, Vinod Kone  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.0.4.
>
>
> 1.0.4 includes the following:
>
> 
> 
>
> * [MESOS-2537] - AC_ARG_ENABLED checks are broken
>
>
> * [MESOS-6606] - Reject optimized builds with libcxx before 3.9
>
>
> * [MESOS-7008] - Quota not recovered from registry in empty cluster.
>
>
> * [MESOS-7366] - Agent sandbox gc could accidentally delete the entire
> persistent volume content.
>
> * [MESOS-7383] - Docker executor logs possibly sensitive parameters.
>
>
>
> 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=1.0.4-rc1
>
> 
> 
>
>
> The candidate for Mesos 1.0.4 release is available at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz
>
>
> The tag to be voted on is 1.0.4-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.4-rc1
>
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/
> mesos-1.0.4.tar.gz.md5
>
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/
> mesos-1.0.4.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-1184
>
>
> Please vote on releasing this package as Apache Mesos 1.0.4!
>
>
> The vote is open until Thu Apr 20 15:42:56 PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
>
> [ ] +1 Release this package as Apache Mesos 1.0.4
>
> [ ] -1 Do not release this package because ...
>
>
> Thanks,
>

[VOTE] Release Apache Mesos 1.0.4 (rc1)

[Vinod Kone]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.0.4.


1.0.4 includes the following:



* [MESOS-2537] - AC_ARG_ENABLED checks are broken


* [MESOS-6606] - Reject optimized builds with libcxx before 3.9


* [MESOS-7008] - Quota not recovered from registry in empty cluster.


* [MESOS-7366] - Agent sandbox gc could accidentally delete the entire
persistent volume content.

* [MESOS-7383] - Docker executor logs possibly sensitive parameters.



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=1.0.4-rc1




The candidate for Mesos 1.0.4 release is available at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz


The tag to be voted on is 1.0.4-rc1:

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.4-rc1


The MD5 checksum of the tarball can be found at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz.md5


The signature of the tarball can be found at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.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-1184


Please vote on releasing this package as Apache Mesos 1.0.4!


The vote is open until Thu Apr 20 15:42:56 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.


[ ] +1 Release this package as Apache Mesos 1.0.4

[ ] -1 Do not release this package because ...


Thanks,

[Design doc] RPC: Fault domains in Mesos

[Neil Conway]

Folks,

I'd like to enhance Mesos to support a first-class notion of "fault
domains" -- i.e., identifying the "rack" and "region" (DC) where a
Mesos agent or master is located. The goal is to enable two main
features:

(1) To make it easier to write "rack-aware" Mesos frameworks that are
portable to different Mesos clusters.

(2) To improve the experience of configuring Mesos with a set of
masters and agents in one DC, and another pool of "remote" agents in a
different DC.

For more information, please see the design doc:

https://docs.google.com/document/d/1gEugdkLRbBsqsiFv3urRPRNrHwUC-i1HwfFfHR_MvC8

I'd love any feedback, either directly on the Google doc or via email.

Thanks,
Neil