Hi Travis
Thanks for narrowing down the issue. I had a brief look at your patch and it
looks like it relies on adding delay before inspect is called. Although that
might work mostly, I am wondering if that is the right solution. It would be
better if we can have a timeout (using ‘after’ on the
How about rename submitting-a-patch to CONTRIBUTING.md or
create CONTRIBUTING.md which would show when user create pull request in
github? Furthermore, because I saw we also submit doc through Review board,
how about disable pull request in Github which let user confuse?
On Wed, Feb 3, 2016 at 4:4
I've noticed that in the published mesos packages [1] & docker images [2]
that the version name isn't simply:
- mesos_0.27.0.ubuntu1404_amd64
Instead it has the form of:
- mesos_0.27.0*-0.2.190*.ubuntu1404_amd64
Here are a few more examples of this numeric suffix:
- 0.27.0 -> 0.27.0-
I agree we should remove this text after some period of time has
passed since that version of Mesos was released; it is quite
distracting.
The proper long-term fix is probably to have version-specific docs. So
all the documentation at
/documentation/v0.27/...
would implicitly discuss the feature
Hi all!
In our docs, you find such sentences as:
"Mesos 0.15.0 added support for framework authentication, and 0.19.0 added
slave authentication."
It's a minor point, but I wonder how long we should maintain such version
numbers in the docs? In the example above, my feeling is that we are far
eno
Just restored the file.
On Tue, Feb 2, 2016 at 4:43 PM, Vinod Kone wrote:
> We moved the 'site' directory from svn into our git repo to make it easy
> for contributors to submit patches for the website.
>
> Is it possible for whatever is looking at the doap file to look at
> git/mesos/site instea
We moved the 'site' directory from svn into our git repo to make it easy
for contributors to submit patches for the website.
Is it possible for whatever is looking at the doap file to look at
git/mesos/site instead?
Please fix the DOAP file location
-- Forwarded message --
From: Cron Daemon
Date: 2 February 2016 at 21:31
Subject: Cron /x1/home/apsite/wrkdir/bin/build.sh
To: site-...@apache.org
projects_21.log:Failed to get
'http://svn.apache.org/repos/asf/mesos/site/doap.rdf' Status =
I'd like to initiate a discussion on the following issue:
https://issues.apache.org/jira/browse/MESOS-4581
I've included a lot of detail in the JIRA, and would rather not reiterate _all_
of it here on the list, but in short:
We are experiencing an issue when launching docker containers from mar
OK then, Thanks.
Consider this message a formal request for contributor permissions so that I
can assign the JIRA to myelf.
Travis
-Original Message-
From: Kapil Arya [mailto:ka...@mesosphere.io]
Sent: Tuesday, February 2, 2016 3:04 PM
To: dev
Subject: Re: Shephard Reqeust: patch for
Thanks for the explanation, Greg!!
Travis,
Thanks for contributing to Mesos. Please go through the contributor
guidelines as suggested by
Greg. I can then shepherd the patch for you.
Best,
Kapil
On Tue, Feb 2, 2016 at 2:56 PM, Greg Mann wrote:
> Hi Travis,
> Thanks for your contribution! It's
Hi Travis,
Thanks for your contribution! It's always great to see new contributors :-)
A couple things regarding your patch:
Please have a look at the contribution guidelines here:
http://mesos.apache.org/documentation/latest/submitting-a-patch/
The standard protocol when addressing a JIRA issue
Hi folks,
On behalf of the GPU working group [1] I'd like to share a design doc for
adding some initial support for GPU resources in Mesos:
JIRA Epic: https://issues.apache.org/jira/browse/MESOS-4424
Design Doc:
https://docs.google.com/document/d/10GJ1A80x4nIEo8kfdeo9B11PIbS1xJrrB4Z373Ifkpo/edit
Thanks for starting the discussion about this Evers! Supporting IPv6 has
been a long awaited feature for Mesos, so glad to see that you are
interested in working on this.
I would also vote for #1 because it seems to get us far with minimal code
changes. There is already a #networking working group
Hello All,
I am requesting a review of a patch to MESOS-4370. Here are all of the
pertinent links:
https://issues.apache.org/jira/browse/MESOS-4370
https://reviews.apache.org/r/43093/
https://github.com/apache/mesos/pull/90
I have tagged Benjamin Hindman as a reviewer already on the review boar
I just wanted to note that there are some existing packages doing this
already.
For example the thunderbird-dev package on ubuntu (>= trusty) has
several private library headers in e.g. /usr/include/thunderbird/gmock
or /usr/include/thunderbird/google/protobuf
On 27.01.2016 16:28, Kapil Arya wrot
16 matches
Mail list logo
