Re: CMake build refactoring

[Benno Evers]

Hi Andrew,

thanks for working on this, it looks very nice.

Is there a policy on how to handle changes to the build system before the
official deprecation of autotools? I.e., should should reviewers require
that new features are added only to autoconf, only to CMake, or to both?

Thanks,
Benno

On Sat, Aug 26, 2017 at 2:39 AM,  wrote:

> Hi Zhitao,
>
> 1) I talked with Joe and confirmed that we're targeting 1.5 for this chain.
>
> 2) For Mesos modules, the included example modules are built, but I don't
> have an external example. I think the easiest approach to doing so is to
> include Mesos as a submodule and then `add_subdirectory(mesos)`, which
> would bring the target for `libmesos` into your graph to build the module
> against. I can work with anyone willing to create an example.
>
> 3) Yes, that is the plan. The JIRA issue tracking CMake is MESOS-898, and
> the last thread about the (eventual) deprecation of Autotools is here:
> https://mail-archives.apache.org/mod_mbox/mesos-dev/201703.mbox/browser
>
> Thanks,
>
> Andrew
>
>
> On 08/25/2017 2:40 pm, Zhitao Li wrote:
>
>> Hi Andrew,
>>
>> Thank you for the great work. Really looking forward to see a more
>> structured dependency graph.
>>
>> A couple of questions:
>>
>> 1) is there a target version of this work? Will the chain land on 1.5?
>>
>> 2) For people who maintains Mesos modules, is there a example build of how
>> people can arrange their build?
>>
>> 3) Is there plan to make CMake the only supported build system? If yes,
>> what's the graduation standard?
>>
>> Thanks!
>>
>> On Fri, Aug 25, 2017 at 1:00 PM, Vinod Kone  wrote:
>>
>> +1
>>>
>>> On Fri, Aug 25, 2017 at 12:08 PM,  wrote:
>>>
>>> > I have the Java libraries building now on both Linux and Windows
>>> (though
>>> > the initial setup on Windows is a bit annoying to get all the tools in
>>> the
>>> > right place, I'd like to follow up this chain with a `docs/cmake.md`
>>> with
>>> > all the odd little bits of information).
>>> >
>>> > I also enabled the ZooKeeper unit tests (which I needed in order to
>>> > integration test the patches that went upstream to ZooKeeper to give
>>> their
>>> > C Client library a CMake build, too).
>>> >
>>> > Furthermore, with the Java library, I've successfully run Marathon
>>> against
>>> > CMake built Mesos libraries on Linux.
>>> >
>>> > I do not have the Python libraries building yet, and there is a "Java
>>> > examples" library that is not yet built. I'll make sure to file issues
>>> to
>>> > update these.
>>> >
>>> > Joe is working to update the Mesosphere CI, I will check with him about
>>> > updating `docker-build.sh`.
>>> >
>>> > Thanks Vinod!
>>> >
>>> >
>>> > On 08/25/2017 11:59 am, Vinod Kone wrote:
>>> >
>>> >> This is great to hear. Thanks for your perseverance on making this
>>> happen
>>> >> Andy!
>>> >>
>>> >> Btw, do we build Java and Python libraries too now?
>>> >>
>>> >> Once we land the CMake changes, lets make sure to update
>>> >> `support/docker-build.sh` to make sure it is continuously being tested
>>> on
>>> >> our CI.
>>> >>
>>> >> On Fri, Aug 25, 2017 at 11:47 AM,  wrote:
>>> >>
>>> >> Hello Mesos developers,
>>> >>>
>>> >>> I wanted to take the time to announce a (long) patch chain that fixes
>>> up
>>> >>> the CMake build system. There were a lot of open bugs due to the
>>> initial
>>> >>> design (and constraints of CMake 2), and by moving to CMake 3, I was
>>> able
>>> >>> to rewrite the CMake build in a target-based dependency graph manner
>>> (the
>>> >>> way CMake is meant to be used).
>>> >>>
>>> >>> The very end of the chain is here: https://reviews.apache.org/r/6
>>> 1753/
>>> >>>
>>> >>> Joseph Wu is currently shepherding it. That final patch includes the
>>> what
>>> >>> and the why explanation of this patch series.
>>> >>>
>>> >>> My main guideline in this effort was MESOS-3576, which pointed out
>>> the
>>> >>> incorrectness of the link flags generated by CMake. This has been
>>> >>> resolved,
>>> >>> and moreover, a significant amount of superfluous CMake code was
>>> deleted
>>> >>> (that final patch was about a 4 to 1 ratio of deletions to adds).
>>> >>>
>>> >>> I took a two-phase approach to this reworking. The first phase
>>> imported
>>> >>> all of our third party dependencies correctly. Instead of linking to
>>> >>> these
>>> >>> dependencies by manually including their various include/library
>>> >>> directories and compilation/link flags, each dependency was added to
>>> the
>>> >>> CMake graph as an imported target. All necessary information for
>>> linking
>>> >>> to
>>> >>> the dependency is recorded in its target, and used is transitively
>>> passed
>>> >>> to targets which take it as dependency by CMake. Adding a new
>>> dependency
>>> >>> is
>>> >>> now relatively simple, with many easy-to-replicate patterns available
>>> in
>>> >>> 3rdparty/CMakeLists.txt.
>>> >>>
>>> >>> An important note is 

[VOTE] Release Apache Mesos 1.4.0 (rc2)

[Kapil Arya]

Hi all,

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


1.4.0 includes the following:


  * Ability to recover the agent ID after a host reboot.
  * File-based and image-pull secrets.
  * Linux ambient and bounding capabilities support.
  * Ability to efficiently measure disk usage without enforcing usage
constraints.
  * Hierarchical resource allocation roles. [EXPERIMENTAL]

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.4.0-rc2



The candidate for Mesos 1.4.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/mesos-1.4.0.tar.gz

The tag to be voted on is 1.4.0-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/mesos-1.4.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/mesos-1.4.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-1210

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Thursday, Aug 31 11:59 AM PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.4.0
[ ] -1 Do not release this package because ...

Thanks,
Anand and Kapil

[VOTE] Release Apache Mesos 1.4.0 (rc3)

[Kapil Arya]

Hi all,

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

1.4.0 includes the following:

  * Ability to recover the agent ID after a host reboot.
  * File-based and image-pull secrets.
  * Linux ambient and bounding capabilities support.
  * Ability to efficiently measure disk usage without enforcing usage
constraints.
  * Hierarchical resource allocation roles. [EXPERIMENTAL]

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.4.0-rc3



The candidate for Mesos 1.4.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz

The tag to be voted on is 1.4.0-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc3

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.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-1212

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.4.0
[ ] -1 Do not release this package because ...

Thanks,
Anand and Kapil

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

[Kapil Arya]

Hi All,

Due to a discrepancy in the CHANGELOG, we are retracting this release
candidate and will put out a new release candidate for voting in a little
while.

Best,
Anand and Kapil

On Mon, Aug 28, 2017 at 12:44 PM, Kapil Arya  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
>
>
> 1.4.0 includes the following:
> 
> 
>   * Ability to recover the agent ID after a host reboot.
>   * File-based and image-pull secrets.
>   * Linux ambient and bounding capabilities support.
>   * Ability to efficiently measure disk usage without enforcing usage
> constraints.
>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
>
> 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.4.0-rc2
> 
>
>
> The candidate for Mesos 1.4.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/mesos-1.4.0.tar.gz
>
> The tag to be voted on is 1.4.0-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc2
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/
> mesos-1.4.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/
> mesos-1.4.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-1210
>
> Please vote on releasing this package as Apache Mesos 1.4.0!
>
> The vote is open until Thursday, Aug 31 11:59 AM PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.4.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Anand and Kapil
>

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

[Yan Xu]

Also the libprocess refactor seems to have stability issues:
https://issues.apache.org/jira/browse/MESOS-7921

CI failures this crash caused:
https://lists.apache.org/list.html?bui...@mesos.apache.org:lte=1M:process%3A%3AEventQueue%3A%3AConsumer%3A%3Aempty%28%29%20

---
Jiang Yan Xu  | @xujyan 

On Mon, Aug 28, 2017 at 12:01 PM, Michael Park  wrote:

> -1
>
> I found MESOS-7922 ,
> which is an issue around the communication between
> old masters and new agents. Currently, the new agent re-registers with
> the tasks and executors in the new format. The new master conditionally
> upgrades the resources depending on whether the agent has the
> RESERVATION_REFINEMENT capability, but the old master does not know
> to this. The old master would incorrectly interpret any reserved resources
> in the tasks / executors as unreserved.
>
> On Mon, Aug 28, 2017 at 10:32 AM Kapil Arya  wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
>>
>> 1.4.0 includes the following:
>> 
>> 
>>   * Ability to recover the agent ID after a host reboot.
>>   * File-based and image-pull secrets.
>>   * Linux ambient and bounding capabilities support.
>>   * Ability to efficiently measure disk usage without enforcing usage
>> constraints.
>>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
>>
>> 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.4.0-rc3
>> 
>>
>>
>> The candidate for Mesos 1.4.0 release is available at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz
>>
>> The tag to be voted on is 1.4.0-rc3:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc3
>>
>> The MD5 checksum of the tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
>> mesos-1.4.0.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
>> mesos-1.4.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-1212
>>
>> Please vote on releasing this package as Apache Mesos 1.4.0!
>>
>> The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 1.4.0
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>> Anand and Kapil
>>
>

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

[Michael Park]

-1

I found MESOS-7922 ,
which is an issue around the communication between
old masters and new agents. Currently, the new agent re-registers with
the tasks and executors in the new format. The new master conditionally
upgrades the resources depending on whether the agent has the
RESERVATION_REFINEMENT capability, but the old master does not know
to this. The old master would incorrectly interpret any reserved resources
in the tasks / executors as unreserved.

On Mon, Aug 28, 2017 at 10:32 AM Kapil Arya  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
>
> 1.4.0 includes the following:
>
> 
>   * Ability to recover the agent ID after a host reboot.
>   * File-based and image-pull secrets.
>   * Linux ambient and bounding capabilities support.
>   * Ability to efficiently measure disk usage without enforcing usage
> constraints.
>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
>
> 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.4.0-rc3
> 
>
>
> The candidate for Mesos 1.4.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz
>
> The tag to be voted on is 1.4.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc3
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.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-1212
>
> Please vote on releasing this package as Apache Mesos 1.4.0!
>
> The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.4.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Anand and Kapil
>

RE: CMake build refactoring

[Jeff Coffler]

Looks like Andy didn't answer this, so I will.

Currently Linux builds still use autotools but can use cmake. Buildbot uses 
autotools for Linux. Windows builds exclusively uses cmake.

End result: For now, reviewers should insure that changes which affect files 
(new source files, new header files for autotools) should work in both autoconf 
and cmake. This will continue until final deprecation of autotools. I'm unsure 
when that will be, but it'll be a while.

If you don't do that, then you will break some build (and some buildbot).

/Jeff

-Original Message-
From: Benno Evers [mailto:bev...@mesosphere.com] 
Sent: Monday, August 28, 2017 2:41 AM
To: dev@mesos.apache.org
Subject: Re: CMake build refactoring

Hi Andrew,

thanks for working on this, it looks very nice.

Is there a policy on how to handle changes to the build system before the 
official deprecation of autotools? I.e., should should reviewers require that 
new features are added only to autoconf, only to CMake, or to both?

Thanks,
Benno

On Sat, Aug 26, 2017 at 2:39 AM,  wrote:

> Hi Zhitao,
>
> 1) I talked with Joe and confirmed that we're targeting 1.5 for this chain.
>
> 2) For Mesos modules, the included example modules are built, but I 
> don't have an external example. I think the easiest approach to doing 
> so is to include Mesos as a submodule and then 
> `add_subdirectory(mesos)`, which would bring the target for `libmesos` 
> into your graph to build the module against. I can work with anyone willing 
> to create an example.
>
> 3) Yes, that is the plan. The JIRA issue tracking CMake is MESOS-898, 
> and the last thread about the (eventual) deprecation of Autotools is here:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail-
> archives.apache.org%2Fmod_mbox%2Fmesos-dev%2F201703.mbox%2Fbrowser
> a=02%7C01%7CJeff.Coffler%40microsoft.com%7Ceaf570e831614a3bac2608d4edf
> 8fc46%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636395101029885531&
> sdata=vqqfe%2BQJqOoh6ZMp15W4zHO0iNj3WFYM7nkRU6ovgxE%3D=0
>
> Thanks,
>
> Andrew
>
>
> On 08/25/2017 2:40 pm, Zhitao Li wrote:
>
>> Hi Andrew,
>>
>> Thank you for the great work. Really looking forward to see a more 
>> structured dependency graph.
>>
>> A couple of questions:
>>
>> 1) is there a target version of this work? Will the chain land on 1.5?
>>
>> 2) For people who maintains Mesos modules, is there a example build 
>> of how people can arrange their build?
>>
>> 3) Is there plan to make CMake the only supported build system? If 
>> yes, what's the graduation standard?
>>
>> Thanks!
>>
>> On Fri, Aug 25, 2017 at 1:00 PM, Vinod Kone  wrote:
>>
>> +1
>>>
>>> On Fri, Aug 25, 2017 at 12:08 PM,  wrote:
>>>
>>> > I have the Java libraries building now on both Linux and Windows
>>> (though
>>> > the initial setup on Windows is a bit annoying to get all the 
>>> > tools in
>>> the
>>> > right place, I'd like to follow up this chain with a 
>>> > `docs/cmake.md`
>>> with
>>> > all the odd little bits of information).
>>> >
>>> > I also enabled the ZooKeeper unit tests (which I needed in order 
>>> > to integration test the patches that went upstream to ZooKeeper to 
>>> > give
>>> their
>>> > C Client library a CMake build, too).
>>> >
>>> > Furthermore, with the Java library, I've successfully run Marathon
>>> against
>>> > CMake built Mesos libraries on Linux.
>>> >
>>> > I do not have the Python libraries building yet, and there is a 
>>> > "Java examples" library that is not yet built. I'll make sure to 
>>> > file issues
>>> to
>>> > update these.
>>> >
>>> > Joe is working to update the Mesosphere CI, I will check with him 
>>> > about updating `docker-build.sh`.
>>> >
>>> > Thanks Vinod!
>>> >
>>> >
>>> > On 08/25/2017 11:59 am, Vinod Kone wrote:
>>> >
>>> >> This is great to hear. Thanks for your perseverance on making 
>>> >> this
>>> happen
>>> >> Andy!
>>> >>
>>> >> Btw, do we build Java and Python libraries too now?
>>> >>
>>> >> Once we land the CMake changes, lets make sure to update 
>>> >> `support/docker-build.sh` to make sure it is continuously being 
>>> >> tested
>>> on
>>> >> our CI.
>>> >>
>>> >> On Fri, Aug 25, 2017 at 11:47 AM,  wrote:
>>> >>
>>> >> Hello Mesos developers,
>>> >>>
>>> >>> I wanted to take the time to announce a (long) patch chain that 
>>> >>> fixes
>>> up
>>> >>> the CMake build system. There were a lot of open bugs due to the
>>> initial
>>> >>> design (and constraints of CMake 2), and by moving to CMake 3, I 
>>> >>> was
>>> able
>>> >>> to rewrite the CMake build in a target-based dependency graph 
>>> >>> manner
>>> (the
>>> >>> way CMake is meant to be used).
>>> >>>
>>> >>> The very end of the chain is here: 
>>> >>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>> >>> Freviews.apache.org%2Fr%2F6=02%7C01%7CJeff.Coffler%40micros
>>> >>> oft.com%7Ceaf570e831614a3bac2608d4edf8fc46%7C72f988bf86f141af91a
>>> 

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

[tommy xiao]

-1

2017-08-29 3:29 GMT+08:00 Yan Xu :

> Also the libprocess refactor seems to have stability issues:
> https://issues.apache.org/jira/browse/MESOS-7921
>
> CI failures this crash caused:
> https://lists.apache.org/list.html?bui...@mesos.apache.org:
> lte=1M:process%3A%3AEventQueue%3A%3AConsumer%3A%3Aempty%28%29%20
>
> ---
> Jiang Yan Xu  | @xujyan 
>
> On Mon, Aug 28, 2017 at 12:01 PM, Michael Park  wrote:
>
> > -1
> >
> > I found MESOS-7922 ,
> > which is an issue around the communication between
> > old masters and new agents. Currently, the new agent re-registers with
> > the tasks and executors in the new format. The new master conditionally
> > upgrades the resources depending on whether the agent has the
> > RESERVATION_REFINEMENT capability, but the old master does not know
> > to this. The old master would incorrectly interpret any reserved
> resources
> > in the tasks / executors as unreserved.
> >
> > On Mon, Aug 28, 2017 at 10:32 AM Kapil Arya  wrote:
> >
> >> Hi all,
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
> >>
> >> 1.4.0 includes the following:
> >> 
> >> 
> >>   * Ability to recover the agent ID after a host reboot.
> >>   * File-based and image-pull secrets.
> >>   * Linux ambient and bounding capabilities support.
> >>   * Ability to efficiently measure disk usage without enforcing usage
> >> constraints.
> >>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
> >>
> >> 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.4.0-rc3
> >> 
> 
> >>
> >>
> >> The candidate for Mesos 1.4.0 release is available at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
> mesos-1.4.0.tar.gz
> >>
> >> The tag to be voted on is 1.4.0-rc3:
> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=
> commit;h=1.4.0-rc3
> >>
> >> The MD5 checksum of the tarball can be found at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
> >> mesos-1.4.0.tar.gz.md5
> >>
> >> The signature of the tarball can be found at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
> >> mesos-1.4.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-1212
> >>
> >> Please vote on releasing this package as Apache Mesos 1.4.0!
> >>
> >> The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if
> a
> >> majority of at least 3 +1 PMC votes are cast.
> >>
> >> [ ] +1 Release this package as Apache Mesos 1.4.0
> >> [ ] -1 Do not release this package because ...
> >>
> >> Thanks,
> >> Anand and Kapil
> >>
> >
>



-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

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

[Benjamin Mahler]

-1 due to https://issues.apache.org/jira/browse/MESOS-7921

Thanks for reporting this Yan, it unfortunately went unnoticed despite CI
failures since Aug 3rd.

On Mon, Aug 28, 2017 at 12:29 PM, Yan Xu  wrote:

> Also the libprocess refactor seems to have stability issues:
> https://issues.apache.org/jira/browse/MESOS-7921
>
> CI failures this crash caused:
> https://lists.apache.org/list.html?bui...@mesos.apache.org:l
> te=1M:process%3A%3AEventQueue%3A%3AConsumer%3A%3Aempty%28%29%20
>
> ---
> Jiang Yan Xu  | @xujyan 
>
> On Mon, Aug 28, 2017 at 12:01 PM, Michael Park  wrote:
>
> > -1
> >
> > I found MESOS-7922 ,
> > which is an issue around the communication between
> > old masters and new agents. Currently, the new agent re-registers with
> > the tasks and executors in the new format. The new master conditionally
> > upgrades the resources depending on whether the agent has the
> > RESERVATION_REFINEMENT capability, but the old master does not know
> > to this. The old master would incorrectly interpret any reserved
> resources
> > in the tasks / executors as unreserved.
> >
> > On Mon, Aug 28, 2017 at 10:32 AM Kapil Arya  wrote:
> >
> >> Hi all,
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
> >>
> >> 1.4.0 includes the following:
> >> 
> >> 
> >>   * Ability to recover the agent ID after a host reboot.
> >>   * File-based and image-pull secrets.
> >>   * Linux ambient and bounding capabilities support.
> >>   * Ability to efficiently measure disk usage without enforcing usage
> >> constraints.
> >>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
> >>
> >> 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.4.0-rc3
> >> 
> 
> >>
> >>
> >> The candidate for Mesos 1.4.0 release is available at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos
> -1.4.0.tar.gz
> >>
> >> The tag to be voted on is 1.4.0-rc3:
> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
> ;h=1.4.0-rc3
> >>
> >> The MD5 checksum of the tarball can be found at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
> >> mesos-1.4.0.tar.gz.md5
> >>
> >> The signature of the tarball can be found at:
> >> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/
> >> mesos-1.4.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-1212
> >>
> >> Please vote on releasing this package as Apache Mesos 1.4.0!
> >>
> >> The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if
> a
> >> majority of at least 3 +1 PMC votes are cast.
> >>
> >> [ ] +1 Release this package as Apache Mesos 1.4.0
> >> [ ] -1 Do not release this package because ...
> >>
> >> Thanks,
> >> Anand and Kapil
> >>
> >
>