As if you
don't plan on following up on this yourself in the near future?
—
*Joris Van Remoortere*
Mesosphere
On Mon, Mar 27, 2017 at 4:03 PM, Jeff Coffler <
jeff.coff...@microsoft.com.invalid> wrote:
> I had previously send an E-Mail to the Mesos DEV list on Tue 2/14/2017
> 1
Hello developers,
It has come that time again where our review backlog got too long.
As we have done previously, I've discarded older reviews. This time all
reviews that had been inactive for over 2 months.
If I discarded one of your reviews you should have received an e-mail
directed at the addr
file reduces the compile time.
A good example of heave .o files are the mesos tests that scan close to all
of stout / libprocess for each test file.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Feb 14, 2017 at 4:49 PM, Jeff Coffler <
jeff.coff...@microsoft.com.invalid> wrote:
> Hi Neil,
&
This looks interesting.
I would recommend creating a JIRA and attaching it to the review.
One preliminary question: Can we not probe the filesystem to identify
whether it is a RAM_FS? Why do we need to add administrator flags for this?
—
*Joris Van Remoortere*
Mesosphere
On Wed, Dec 28, 2016
derstanding whether you mean leaving the message unset, or
the field?
—
*Joris Van Remoortere*
Mesosphere
On Thu, Feb 2, 2017 at 3:06 PM, Yan Xu wrote:
> With protobuf you can specify custom default values for scalar types
> (proto2 at least) but not message types, e.g.,
>
>
These 2 JIRAs might be helpful:
https://issues.apache.org/jira/browse/MESOS-786
https://issues.apache.org/jira/browse/MESOS-6249
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jan 17, 2017 at 5:31 PM, Zhitao Li wrote:
> Hi,
>
> I'm helping a scheduler author to deal with a prob
is not too high for current developers on Apple systems then this is
a pretty easy fix :-)
Joris
—
*Joris Van Remoortere*
Mesosphere
On Tue, Dec 20, 2016 at 5:02 PM, Vinod Kone wrote:
> A consequence of using `__thread` on Apple is that initializers for thread
> locals are require
tting the impression that it's reasonable to make this change without
a deprecation cycle. Please let me know if you (anyone) disagrees.
—
*Joris Van Remoortere*
Mesosphere
On Mon, Dec 19, 2016 at 2:17 PM, Zameer Manji wrote:
> I believe this thread_local support is in XCode 8.2. From
more CPU the amortized cost of the idle executors would not
be such a big deal.
—
*Joris Van Remoortere*
Mesosphere
On Mon, Dec 19, 2016 at 11:26 AM, Timothy Chen wrote:
> Hi Chawla,
>
> One possible reason is that Mesos fine grain mode also takes up cores
> to run the executor per
@Zhitao are you looking specifically for structure or just for tagging?
glog does already have support for custom tags in the header. I don't know
if this is enough for your use case though.
—
*Joris Van Remoortere*
Mesosphere
On Mon, Dec 19, 2016 at 9:58 AM, James Peach wrote:
>
>
Is my understanding incorrect regarding the ability to upgrade the compiler
version on Yosemite and El Capitan without requiring a full system upgrade?
@Mpark are you making a case for not updating to `thread_local` just yet?
—
*Joris Van Remoortere*
Mesosphere
On Fri, Dec 16, 2016 at 11:11 AM
to whether requiring this
toolchain update is acceptable, and if we need a deprecation period or if
we can just make this change now.
I am leaning towards no deprecation period as I am not aware of production
environments running on systems that define `__APPLE__`.
—
*Joris Van Remoortere
e in the agent configuration? I think we highly recommend that you
do this in production to prevent accidental incompatibility of resources
even without an actual hardware change. Historically there were some issues
reported where the kernel reported a slightly different amount of memory
after reboo
safe?
Joris
—
*Joris Van Remoortere*
Mesosphere
On Mon, Dec 5, 2016 at 1:16 PM, James Peach wrote:
>
> > On Dec 2, 2016, at 10:54 PM, Jie Yu wrote:
> >
> > Another tip. If you are on macOS sierra, you might notice the linking is
> > extremely slow using the defau
only catch some of the manifestations.
—
*Joris Van Remoortere*
Mesosphere
On Mon, Dec 12, 2016 at 7:56 AM, Neil Conway wrote:
> Hi Joris,
>
> Fair point: I didn't deliberately set out to change the behavior for
> duplicate task IDs. Rather, it was a consequence of switc
x27;m wondering why a multi-hashmap is not sufficient. This would be clear if
you were explicitly *trying* to get rid of duplicates of course :-)
Thanks,
Joris
—
*Joris Van Remoortere*
Mesosphere
On Fri, Dec 9, 2016 at 7:08 AM, Neil Conway wrote:
> Folks,
>
> The master stores a cac
Switch to the user that the agent is running as, and the directory from
which it is executing and ensure that you can find hadoop. For example by
running
`which hadoop`. This may be a PATH or JAVA_HOME issue?
—
*Joris Van Remoortere*
Mesosphere
On Thu, Nov 10, 2016 at 6:29 AM, Yu Wei wrote
still seem like an issue if it's not a requirement but just a
broadening of possibilities?
—
*Joris Van Remoortere*
Mesosphere
On Wed, Nov 2, 2016 at 1:49 PM, Zameer Manji wrote:
> Joris,
>
> You make a good point. However, I'm not convinced that `CommandInfo` should
> be
I think I'm missing why we would spend energy controlling the leveldb
compaction.
I thought leveldb was used for convenience, and its log structured merge
algorithm was just a consequence.
Why not spend energy writing an append only file as opposed to optimizing
compaction of an algorithm we d
-1
Based on my message in the 1.1.0 vote:
My understanding after speaking with BenM is that the fix for
https://issues.apache.org/jira/browse/MESOS-6457 should be straight forward.
I don't think the cost of debugging and fixing production systems if they
run into this is worth skipping an easy f
-1
My understanding after speaking with BenM is that the fix for
https://issues.apache.org/jira/browse/MESOS-6457 should be straight forward.
I don't think the cost of debugging and fixing production systems if they
run into this is worth skipping an easy fix. I have re-targeted the JIRA to
1.1.0
executors then it would be great for there
to be standard way to pass command information to them.
The current model works well in a 1-1 mapping between framework and
executor binaries. In a world where that is 1-N it means all N executors
have to use the same method of passing the command.
—
*Joris Van
ng experience for them to find
out that is not the case.
—
*Joris Van Remoortere*
Mesosphere
On Fri, Oct 14, 2016 at 3:11 PM, Neil Conway wrote:
> Hi folks,
>
> I'd like input from individuals who currently use frameworks but do
> not enable checkpointing.
>
> Backgroun
+1
—
*Joris Van Remoortere*
Mesosphere
On Thu, Oct 13, 2016 at 1:38 PM, Vinod Kone wrote:
> Huge +1. Thanks for taking ownership of this.
>
> On Thu, Oct 13, 2016 at 1:34 PM, Michael Park wrote:
>
> > I would like to try to get the community syncs back on track. They h
larger reasons (for
example when we wanted c++11) we'll need to propose the change and provide
some deprecation period regardless.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Oct 11, 2016 at 4:53 AM, Evers Benno wrote:
> To be honest, I still think it's a pretty big pain to req
ID,
Master ID, etc.
—
*Joris Van Remoortere*
Mesosphere
On Wed, Oct 5, 2016 at 11:34 AM, Benjamin Hindman
wrote:
> How does adding the filename extension help with the context problem?
>
> On Wed, Oct 5, 2016 at 6:14 AM, Joris Van Remoortere
> wrote:
>
>> This is technic
tually can become IO bound. There are ways to
get around that too. There have been times where an optimized build has
been faster than a debug build.
Joris
—
*Joris Van Remoortere*
Mesosphere
On Tue, Sep 27, 2016 at 6:25 PM, Michael Park wrote:
> On Tue, Sep 27, 2016 at 12:21 PM, Alexander Roj
ad-safe.
> //
> GOOGLE_GLOG_DLL_DECL void SetLogFilenameExtension(
> const char* filename_extension);
@benm @vinod @benh what are your thoughts on actually doing it?
—
*Joris Van Remoortere*
Mesosphere
On Tue, Oct 4, 2016 at 2:39 PM, Zameer Manji wrote:
> I don't know
callgrind results to
find other bottlenecks mentioned earlier in the thread.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jul 12, 2016 at 2:26 AM, Guangya Liu wrote:
> Hi Joris,
>
> For `2x` number, can you please show more detail for how did you do and
> evaluate the test? How did
only quantities in the
Sorter, and that using the existing form of Resources would have led to a
grinding halt if a reservation were made on every machine.
Is there a regular call that is scheduled to discuss this? I think there
are some other folks also working on benchmarks and interested in the
dis
when they don't make sense, or have been
replaced. Many of the ones I closed ended up being irrelevant.
Thanks for all your contributions. I will be engaging with the committers
to get as many of the remaining patches committed as is possible.
Joris
—
*Joris Van Remoortere*
Mesosphere
On Wed,
slack?) when you feel a sufficient explanation
is updated in the patch and I'll schedule time to review them.
Joris
—
*Joris Van Remoortere*
Mesosphere
On Thu, Jul 7, 2016 at 7:20 PM, Dario Rexin wrote:
> A bit more context:
>
> We have a very high number of frameworks on our clus
h reconsidering whether we need to do this hack.
—
*Joris Van Remoortere*
Mesosphere
On Thu, Jul 7, 2016 at 10:15 AM, Guangya Liu wrote:
> Hi Ben and Dario,
>
> The reason that we have "SUPPRESS" call is as following:
> 1) Act as the complement to the current REVIVE call.
I'll take another look at this tomorrow with Joseph.
Thanks for your hard Work!
—
*Joris Van Remoortere*
Mesosphere
On Fri, Jul 1, 2016 at 3:59 AM, Yan Yan YY Hu wrote:
>
> Hi, could anyone help to make further review on 48593(
> https://reviews.apache.org/r/48593/). It is an i
ugh on them with the contributor.
On Wed, Jun 29, 2016 at 8:17 PM, Tomek Janiszewski
wrote:
> How about running CI on all reviews. If patch is stale it probably can't be
> applied, CI will post bad patch and if nobody do any action on that review
> we can close it.
>
> śr.
Hello developers,
Over the last year we've accumulated a significant review backlog. Over the
past month it has been floating around ~600 reviews.
It would be of great help if you could look through your personal list
(Dashboard -> Outgoing -> Open) and identify reviews that are *no longer
releva
Hi Hans,
If you delay, and then the lambda that you schedule is a `defer` on to the
same process, then this accomplishes what you want.
The one caveat is that other functions may be invoked on your actor process
in the mean time.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 28, 2016 at 1:14
I think it would be great to comment in place e.g. `/* required */ optional
`.
It's difficult enough as is to extract the semantics out of the current
Protos. The required helped document which fields were actually required.
—
*Joris Van Remoortere*
Mesosphere
On Thu, Jun 23, 2016 at 2:
n experts have time.
This is a trade-off we should consider. The best option may still be for it
to be in Python, this is why I'm asking if there are particular things that
our helper libraries don't provide which you are leveraging in python.
—
*Joris Van Remoortere*
Mesosphere
On Thu,
+1 for maintaining in repo.
+1 for C++. Are the tools in libprocess not sufficient to make this easy to
write? What is missing that would make it easier to write in C++?
—
*Joris Van Remoortere*
Mesosphere
On Wed, Jun 22, 2016 at 2:24 AM, Zhou Z Xing wrote:
> +1 for keeping it in Mesos r
he App tried to create /Database-backups/ ?
Only the framework as its original user would be able to do that?
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 21, 2016 at 8:25 AM, Jie Yu wrote:
> Hi folks,
>
> Currently, the ownership of the persistent volumes are set to be the same
>
bout the isolation (you likely do in production), then the only
remedy is to restart them.
—
*Joris Van Remoortere*
Mesosphere
On Mon, Jun 20, 2016 at 4:45 AM, Qiang Chen wrote:
> Thanks @Haosdent for the link to explain the shutdown errors. so I can
> ignore this...
>
> @Joris,
>
>
+1 Slack
—
*Joris Van Remoortere*
Mesosphere
On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone wrote:
> Looks like people have jumped the gun here before I sent the email :)
>
> Here is the context. During the community sync we discussed about using
> *Slack* or *HipChat* as our o
ition from the old systemd lack of support to the new
support.
—
*Joris Van Remoortere*
Mesosphere
On Fri, Jun 17, 2016 at 2:35 PM, haosdent wrote:
> Hi, @Qiang.
>
> @Joseph have a nice explain about at Shutdown failed on fd
>
> http://search-hadoop.com/m/0Vlr6pe7qb2MJX8B1&am
you can devise a plan for your upgrade.
Joris
—
*Joris Van Remoortere*
Mesosphere
On Fri, Jun 17, 2016 at 8:28 AM, Qiang Chen wrote:
> Hi all,
>
> I met an issue when upgrading mesos-slave to 0.28.2.
>
> At the process of recovering mesos-slave / framework container stage, it
@Fan,
In the community meeting a question was raised around which frameworks
might be ready to use this.
Can you provide some more context for immediate use cases on the framework
side?
—
*Joris Van Remoortere*
Mesosphere
On Fri, Jun 17, 2016 at 12:51 AM, Du, Fan wrote:
> A couple of ro
nsequences from
doing this.
—
*Joris Van Remoortere*
Mesosphere
On Wed, Jun 15, 2016 at 8:33 PM, meghdoot bhattacharya <
meghdoo...@yahoo.com.invalid> wrote:
> Resending with fixed links.
>
> I wanted to follow up on 2 issues that we discussed few years back on the
> below blog des
With this 4th sorter approach, how does quota work for scarce resources?
—
*Joris Van Remoortere*
Mesosphere
On Thu, Jun 16, 2016 at 11:26 AM, Guangya Liu wrote:
> Hi Ben,
>
> The pre-condition for four stage allocation is that we need to put
> different resources to different so
Your e-mail seems truncated or mangled in some way (at least for me). Could
you please resend it?
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 14, 2016 at 10:00 PM, meghdoot bhattacharya <
meghdoo...@yahoo.com.invalid> wrote:
>
>
> I wanted to follow up on 2 issues that w
your interest is in the determination of the values, as opposed to
their propagation, I would just urge that you keep in mind that we may (as
a project) not want to support this information as the current string
attributes.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 14, 2016 at 3:02 PM, D
and
which values are allowed to change vs. not.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 14, 2016 at 10:04 AM, Aaron Carey wrote:
> #3 would be very helpful for us. Also related:
>
> https://issues.apache.org/jira/browse/MESOS-3059
>
> --
>
> Aaron Carey
> Prod
Hello!
Thanks for sharing your feedback regarding the range performance. Indeed as you
partition things like agent ports heavily this can be detrimental.
We have looked at this in the past, and the right thing to do is indeed to use
the interval set in Stout.
That being said, the reason we have
+dev.
@Fan, I responded on the JIRA with some next steps.
Thanks for bringing this up!
—
*Joris Van Remoortere*
Mesosphere
On Tue, Jun 7, 2016 at 12:58 PM, james wrote:
> On 06/07/2016 09:57 AM, Du, Fan wrote:
>
>>
>>
>> On 2016/6/6 21:27, james wrote:
>>
>
After
https://github.com/apache/mesos/commit/447d814ac80e67f30a0ffe2ee6047d85dc8fc383
the refuse_seconds should not be as dangerous as it used to be.
This was backported to 0.24 and above recently. Without the backported
patch the filter may never take effect when the allocation takes longer
than t
To be clear, BenM's example will result in the total wall-clock time for
the chain to complete, rather than the sum of time actually spent in those
functions.
—
*Joris Van Remoortere*
Mesosphere
On Fri, Apr 22, 2016 at 4:26 PM, Benjamin Mahler wrote:
> Here's an example of using
That is the plan, I think it just hasn't been done yet :-)
—
*Joris Van Remoortere*
Mesosphere
On Thu, Apr 21, 2016 at 9:20 PM, Qian Zhang wrote:
> In that wiki, can we also put the corresponding JIRA ticket link there so
> that folks can take a close look at the projects they are
systemd?
Joris
—
*Joris Van Remoortere*
Mesosphere
On Fri, Apr 15, 2016 at 6:00 PM, Michael Browning
wrote:
> Hi all,
>
> We've run into an interesting issue with Docker and systemd that's
> hampering our attempts to use cfs_quota for CPU isolation with Docker
> cont
nefits of executing multiple `.onAny` calls in parallel
in the future (if we ever need to) outweigh the inconsistency in the API
regarding ordered execution of certain chains (At least as the API is
currently designed).
—
*Joris Van Remoortere*
Mesosphere
On Wed, Mar 30, 2016 at 12:25 AM, Benjamin
ad setting the future to true.
I'd rather discuss and fix the problem, than try to enforce avoiding this
case.
Thoughts?
—
*Joris Van Remoortere*
Mesosphere
On Tue, Mar 29, 2016 at 2:50 AM, Jie Yu wrote:
> Hi,
>
> While digging a bug reported in, I realized an assumption we shou
lve with the current tag-only approach. Joris and Jie
> seem to be hinting at there being a lack of visibility into the progress of
> RCs. Is that the issue we're trying to solve? Collaboration on RC's? I
> haven't done a release in quite some time so it would be great to
gadget to the JIRA release board that
lists all issues that are unresolved and affecting the previous release, in
order of severity.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Mar 22, 2016 at 7:15 AM, Benjamin Mahler wrote:
> Folks,
>
> Our JIRA volume is very high and I'm finding
* we would never want that concept in Mesos.
—
*Joris Van Remoortere*
Mesosphere
On Sun, Mar 20, 2016 at 8:33 PM, Klaus Ma wrote:
> Here's some input :).
>
> If throttling is tolerable but preemption is not, how would that be
> expressed? (Is that supported?)
> [Klaus]: It&#
The SHAs rarely exist on HEAD because we tend to cherry-pick bug fixes into
release candidates.
I'm all for using branches in the repository to put together the release
candidates, as well as have committers consider their bug fixes for some N
number of backport (future LTS) releases.
As Kevin an
an absolute value, then it would be a
bug.
To represent infinity we currently wrap the Duration with an Option. The
None state represents infinity. You can find this in the protobufs.
—
*Joris Van Remoortere*
Mesosphere
On Wed, Mar 9, 2016 at 11:29 PM, Alexander Rojas
wrote:
> IMO durations
e to install the correct version:
$ sudo cat > /etc/yum.repos.d/wandisco-svn.repo <http://opensource.wandisco.com/centos/7/svn-1.9/RPMS/$basearch/
gpgcheck=1
gpgkey=http://opensource.wandisco.com/RPM-GPG-KEY-WANdisco
EOF
—
*Joris Van Remoortere*
Mesosphere
On Mon, Mar 7, 2016 at 7:01 AM, Walt
e/mesos/commits/0.25.1-rc1/src/tests/master_tests.cpp
> >> >
> >> >
> >>
> https://github.com/apache/mesos/commits/0.24.2-rc1/src/tests/master_tests.cpp
> >> >
> >> > Just not:
> >> >
> >> >
> >>
> https://gi
+1 (binding)
On Mon, Feb 29, 2016 at 3:24 PM, Greg Mann wrote:
> +1 (non-binding)
>
> `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL enabled.
> All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> which is a known failure in 0.24.
>
> Cheers,
> Greg
>
>
>
+1 (binding)
Greg's upgrade scripts & CI results
On Tue, Mar 1, 2016 at 4:37 PM, Greg Mann wrote:
> I was also able to successfully test a simple upgrade scenario between
> 0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which I've
> modified slightly and reposted here: https://
+1 (binding)
Greg's upgrade scripts & CI results
On Fri, Mar 4, 2016 at 11:30 AM, Vinod Kone wrote:
> +1 (binding)
>
> On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues wrote:
>
> > I committed a fix for this in:
> >
> >
> https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a7887166
@Michael Browning:
>
> MasterTest.MaxCompletedTasksPerFrameworkFlag [flaky, tracked in
> MESOS-4518]
This is supposed to be fixed in this release. It is concerning that this
came up.
Can you verify this and provide logs to Kevin Klues?
—
*Joris Van Remoortere*
Mesosphere
On Tue, Mar 1
Hi Marco,
It seems Kapil took a look at your reviews, and likely has context to
understand whether this change makes sense. I would suggest that you clean
up the style errors in the reviews, as there are still quite a few.
Thanks!
—
*Joris Van Remoortere*
Mesosphere
On Fri, Feb 26, 2016 at 9
+1 (binding)
with the condition that we fix the flag mixing problem between CXXFLAGS and
--enable-optimize --enable-debug, even if it is to disallow it for now.
I want to avoid surprising behavior with implicit flags such as optimize:
passing irrelevant CXXFLAGS magically turns it into a debug buil
evenly among agents.
—
*Joris Van Remoortere*
Mesosphere
On Wed, Feb 17, 2016 at 9:35 PM, Suteng wrote:
> Alex,
> We don't have test the performance of mesos. But we have develop a
> framework in house, which is like a simplified mesos, use to schedule a
> large number fine
+1 (binding)
- systemd integration testing
- upgrade path testing
- launching and killing 10K tasks
On Wed, Feb 17, 2016 at 6:52 PM, Jörg Schad wrote:
> + 1 (non-binding)
>
> Mac OS: non-root: DockerFetcherPluginTest.INTERNET_CURL_FetchManifest
>
+1
Thanks for taking this on Neil!
—
*Joris Van Remoortere*
Mesosphere
On Fri, Feb 12, 2016 at 11:25 PM, Neil Conway wrote:
> tl;dr:
>
> If you use resource values with more than three decimal digits of
> precision (e.g., you are launching a task that uses 2.5001 CPUs),
>
ch
as not having silent failure.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Feb 9, 2016 at 9:02 PM, Maged Michael
wrote:
> https://issues.apache.org/jira/browse/MESOS-4353
>
> Thanks.
>
If we did feature based releases, we could hold the release for the
documentation.
Since we do time based releases, it so happened that the release went
through before we could get the docs done.
I'll be working on the docs shortly :-)
—
*Joris Van Remoortere*
Mesosphere
On Thu, Feb 4, 20
+1 (binding)
Tested on Ubuntu 15.04:
- Built with clang-3.6 and gcc-4.8.
- Launched 1K agents.
- Launched 100K tasks (slowly) on 100 agents.
- Validated virtual memory set did not grow.
- Validate UI was responsive.
- Validate task recovery with 0.26 Master -> 0.27 Master
Correction to my previous e-mail.
The mutable resource bug is here:
https://issues.apache.org/jira/browse/MESOS-4534
On Wed, Jan 27, 2016 at 11:57 AM, Joris Van Remoortere <
joris.van.remoort...@gmail.com> wrote:
> -1 (binding)
> There is a bug with mutable resource math that sur
-1 (binding)
There is a bug with mutable resource math that surfaced in the allocator
changes, but is also happening elsehwere.
Mpark is currently working on a patch to disallow this behavior in general,
and fix the current issues.
https://issues.apache.org/jira/browse/MESOS-4030
On Wed, Jan 27,
Hello Mesos developers,
You may have noticed some churn in Jira recently around the shepherd
assignment. Specifically, we have unassigned the shepherds for a bunch of
projects. We did this in order to get a better sense of which projects are
being actively shepherded versus having gone stale, and
ng to
external documentation.
—
*Joris Van Remoortere*
Mesosphere
On Thu, Jan 14, 2016 at 4:44 AM, Jörg Schad wrote:
> Hi,
> just a short note about links in our documentation.
> In the current documentation we use three different ways to link between
> different *.md pages:
> 1. [lab
+1
On Wed, Jan 13, 2016 at 1:27 PM, Timothy Chen wrote:
> Hi all,
>
> As we continue with the monthly release cadence, we should be cutting
> a new release a month from the last one (12/16/15), which the next
> version will be 0.27.0.
>
> MPark, Kapil and I are volunteering to be the release man
+1 (binding)
I would like to propose that we bump our minimum supported version for gcc
> from 4.8.0 to 4.8.1. The main motivation behind this is that there are at
> least 2 outstanding reviews on RB that want to use ref-qualifiers <
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2439.
I will. I think Joseph can (and already has) help review this.
—
*Joris Van Remoortere*
Mesosphere
On Tue, Dec 22, 2015 at 11:02 AM, James Peach wrote:
> Hi all,
>
> Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-3909?
>
> Mesos modules depend on picojson, whic
+1 (binding)
From: Till Toenshoff
Date: Thu, Dec 10, 2015 at 2:55 PM
Subject: [VOTE] Release Apache Mesos 0.26.0 (rc5)
To: u...@mesos.apache.org, dev
Hi friends,
we did unfortunately, once again run into an issue that needed immediate
attention (see vote on rc4), hence we have to ask for anot
+1
—
*Joris Van Remoortere*
Mesosphere
On Sun, Dec 13, 2015 at 11:39 AM, Benjamin Mahler wrote:
> std::function becomes std::function?
>
> +1
>
> On Sun, Dec 13, 2015 at 10:55 AM, Jie Yu wrote:
>
> > +1
> >
> > On Sun, Dec 13, 2015 at 10:46 AM,
fixed
—
*Joris Van Remoortere*
Mesosphere
On Tue, Nov 10, 2015 at 9:53 PM, James Peach wrote:
>
> > On Nov 9, 2015, at 10:25 AM, m...@apache.org wrote:
> >
> > Added JSON parsing for Resources.
> >
> >
>
> [snip]
>
> >
> http://git-wip-us
tools.
If there is more than some simple math involved, this may not be a viable
solution.
Joris
—
*Joris Van Remoortere*
Mesosphere
On Fri, Nov 6, 2015 at 11:10 AM, Benjamin Mahler
wrote:
> I raise this because there is a ton of value in keeping our codebase as
> readable as possibl
+1 with all-at-once
—
*Joris Van Remoortere*
Mesosphere
On Thu, Nov 5, 2015 at 9:37 AM, Kapil Arya wrote:
> +1.
>
> I think we should do it all at once as Artem mentioned. This doesn't really
> affect the history (git-blame, etc.) because we are not touching code per
> s
volunteer.
I'm sorry the current impression of the contribution process is laborious.
Mpark and I gave a talk about this at MesosCon EU. Hopefully the material
will be available soon!
Thanks for contributing!
Joris
—
*Joris Van Remoortere*
Mesosphere
On Tue, Oct 20, 2015 at 11:36 PM, Erik
+1 for (a).
—
*Joris Van Remoortere*
Mesosphere
On Tue, Oct 20, 2015 at 3:02 PM, Benjamin Mahler
wrote:
> +1 for (a), in this case the wide sweep only touches the license comments,
> so it won't be disruptive to history.
>
> On Tue, Oct 20, 2015 at 11:59 AM, James Peach wrot
+1 sounds great!
I like the idea of making epics more manageable and the ability to file JIRAs
based on a design doc while still separating the Epic for the MVP from the
further phases.
> On Oct 15, 2015, at 10:11 AM, Bernd Mathiske wrote:
>
> Proposal: in extension of today’s limited two-leve
+1 (binding)
On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen wrote:
> Hi all,
>
> Following up with an RC with the build fix suggested by Kapil:
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
>
>
>
> 0.25.0 includes the following:
>
>
> --
+1 (binding)
On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen
wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
>
>
>
> 0.25.0 includes the following:
>
>
>
>
> * [MESOS-1
+1 I can help triage with you :-)
On Thu, Oct 1, 2015 at 1:44 AM, Till Toenshoff wrote:
> Hi folks,
>
> Bernd and I would like to volunteer for managing the next release 0.26.
>
> The scope and ETA of 0.26 will be discussed today at the Mesos community
> sync - hence more details on this will fo
; Thanks,
>
> Joris, MPark, and Niklas
>
> On Mon, Sep 14, 2015, 9:23 AM Joris Van Remoortere
> wrote:
>
> > Following in the footsteps of the dashboard for the 0.23.0 release,
> > here is the Mesos 0.25.0 Release Dashboard
> > <
> >
> https://issues
a
>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.u1x3j7f3uixf>
>>> .
>>>
>>> Thanks,
>>>
>>> On Thu, Jul 2, 2015 at 11:24 AM, Joris Van Remoortere <
>>> jo...@mesosphere.i
M, Jie Yu wrote:
>>
>>> Joris, I am using CentOS6 with devtoolset-2
>>>
>>> gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC)
>>>
>>> I did a clean build (rebootstrap, reconfigure).
>>>
>>> - Jie
>>>
>>>
>>&g
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/2c277f1c
> > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/2c277f1c
> > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/2c277f1c
> >
> > Branch: refs/heads/master
> > Commit: 2c277f1c0e0dc0a6618
1 - 100 of 471 matches
Mail list logo
