My take (in general I am in favor of comments):
- In my experience, expectations almost always only tell you what's
wrong but not why, i.e., how the test arrives at the condition. Therefore I
almost always need to read the test itself.
- Unlike CHECKs in the main code, tests are sequen
-1 (binding)
Two upgrade blockers, these need to be backported to 1.2.x as well:
https://issues.apache.org/jira/browse/MESOS-7478 (I have a patch already)
https://issues.apache.org/jira/browse/MESOS-7460 (mpark is working on this)
Re: MESOS-7378
Any updates on whether this will be fixed?
On Tue
Github user asfgit closed the pull request at:
https://github.com/apache/mesos/pull/212
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user spchildren opened a pull request:
https://github.com/apache/mesos/pull/212
Add new MUG for Tokyo
I just add the new Tokyo in Japan MUG in communities by Shingo.Kitayama
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/s
-1
I suggest we include this fix in 1.1.2
https://issues.apache.org/jira/browse/MESOS-7471
On Thu, May 4, 2017 at 12:07 PM, Alex Rukletsov wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.1.2.
>
> 1.1.2 includes the following:
> ---
-1
I want to get this fix into 1.3.0
https://issues.apache.org/jira/browse/MESOS-7471
- Jie
On Tue, May 9, 2017 at 1:14 AM, Yan Xu wrote:
> We work around autotools and protobuf bugs and glibc is only harder for
> users and developers to upgrade. :)
>
> I agree that we can establish the minimu
