://mesos.apache.org) will be updated shortly to reflect
this release.
Thanks,
-Adam-
On Wed, Nov 29, 2017 at 6:32 PM, Benjamin Mahler <bmah...@apache.org> wrote:
> +1 (binding)
>
> make check on macOS 10.13.1
>
> On Wed, Nov 29, 2017 at 9:17 PM, Adam Bordelon <a...@mesos
s://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/44/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Success]
> <https://build
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.2.3.
1.2.3 is our last scheduled bug fix release in the 1.2.x branch.
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.2.3-rc1
Please reply to this email if you have pending patches to backport to 1.2.x.
I'm aiming to cut a 1.2.3 next week. This will be the last 1.2.x release.
I see 3 JIRAs targeted for 1.2.3, but none of them look quite ready to land:
=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Failed]
> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-
> Release/38/BUILDTOO
open.mesosphere.
> com/downloads/mesos-rc/#apache-mesos-1.2.2-rc1
>
> The following docker images based on Ubuntu 16.04 are also available:
> * mesosphere/mesos:1.2.2-rc1
> * mesosphere/mesos-master:1.2.2-rc1
> * mesosphere/mesos-agent:1.2.2-rc1
>
> Kapil
>
>
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 1.2.2.
1.2.2 includes the following:
* [MESOS-5187] - The filesystem/linux isolator does not set the
permissions of the
Hi all,
The vote for Mesos 1.2.1 (rc1) has passed with the following votes.
+1 (Binding)
--
Till Toenshoff
Benjamin Mahler
Adam Bordelon
+1 (Non-binding)
--
tommy xiao
There were no 0 or -1 votes.
Please find the release at:
https
FTFY: Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.3.0
On Wed, Jun 7, 2017 at 3:03 AM, Michael Park wrote:
> Hi all,
>
> The vote for Mesos 1.3.0 (rc3) has passed with the
> following votes.
>
> +1 (Binding)
> --
>
//builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/35/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=%28docker%7C%7CHadoop%29&&%28%21ubuntu-us1%29&&%28%21ubuntu-
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.2.1.
1.2.1 is a bug fix release. 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.2.1-rc1
The candidate for Mesos 1.2.1 release is available
patch.
On Mon, Apr 17, 2017 at 5:53 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> Hello Mesos Developers,
>
> It's patch-release time, and we've got 34 patches in the 1.2.x branch
> since we cut 1.2.0-rc2 (2017/02/24) and voted it in as 1.2.0 (2017/03/08).
> We've also got
Hello Mesos Developers,
It's patch-release time, and we've got 34 patches in the 1.2.x branch since
we cut 1.2.0-rc2 (2017/02/24) and voted it in as 1.2.0 (2017/03/08). We've
also got ~10 patches targeted to 1.2.1 that still need to be
resolved/backported:
-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.
>
Hello devs and users,
The vote for Mesos 1.2.0 (rc2) has passed with the following votes:
+1 (Binding)
--
*** Adam B
*** Vinod Kone
*** Joseph Wu
-0
--
*** Jie Yu, for MESOS-7208
There were no -1 votes.
Please find the release at:
/pull/1295
This was then merged into DC/OS 1.9.0-rc2 which passed another suite of
integration tests. Available for testing at
https://dcos.io/releases/1.9.0-rc2/
On Thu, Mar 2, 2017 at 12:02 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> TL;DR: No consensus yet. Let's extend the vote
1)&&(!ubuntu-eu2)/>
> >
> > On Wed, Mar 1, 2017 at 9:24 AM, Greg Mann <g...@mesosphere.io> wrote:
> >
> >> I wanted to give a heads up on a flaky test failure I've encountered
> while
&
Dear Mesos developers and users,
Please vote on releasing the following candidate as Apache Mesos 1.2.0.
1.2.0 includes the following:
* [MESOS-5931] - **Experimental** Support auto backend in Mesos
Containerizer,
auth.[NEEDS DOCS]
- Distributed HTTP(S) and TCP Health Checks [has docs]
- Authz for Agent v1 Operator API [NEEDS DOCS?]
- Teardown unregistered frameworks [NEEDS DOCS?]
Please let me know if I've missed something.
On Thu, Feb 2, 2017 at 2:24 PM, Adam Bordelon <a...@mesosphere.io> wrote:
&
+1 binding
Tests passed against DC/OS 1.8.8 (prerelease), which is based on the Apache
Mesos 1.0.x branch.
https://github.com/dcos/dcos/pull/1210
On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone wrote:
> +1 (binding)
>
> Tested on ASF CI
>
>
> *Revision*:
to 1.3.
Release dashboard: https://issues.apache.org/jira
/secure/Dashboard.jspa?selectPageId=12329897
On Fri, Jan 27, 2017 at 3:45 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> Mesos 1.2.0 status update:
> - 5 blockers
> <https://issues.apache.org/jira/issues/?jql=filter%20%3
apache.org/jira/browse/MESOS-6904>) smell like
"features", so I'll hold off on cutting the rc1 until after they land,
hopefully by Monday. We're getting so close!
Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?
selectPageId=12329897
On Mon, Jan 9, 20
ing JIRAs, and
c) *documenting
your new features.*
Release dashboard:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329897
On Mon, Dec 26, 2016 at 7:04 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> It's about time for Mesos 1.2.0, given our two-month release cadence. I
Technically that Kafka framework is maintained by members of the Mesos
community, not the Apache Mesos PMC/committers specifically, so a PR to the
repo (with an email to this list) would be a reasonable approach. I'm not
even sure that Joe Stein (cc'd) and the other Kafka framework contributors
+ dev@, in case some module developers haven't joined the modules@ list yet.
So this will require code changes (and a recompile) so any module
implementing the previous hook must now use the new hook, potentially
updating to set both environments instead of just the one. Such a hook
compiled
+1 (binding)
We've been running this in our internal soak cluster for a while now, and
it's nice and stable.
P.S. Can we call the result of this vote now?
On Mon, Aug 15, 2016 at 11:45 AM, Zhitao Li wrote:
> +1 (nonbinding)
>
> Deployed a build to smaller testing cluster
Our general strategy is to land things in master first, then the committer
will backport it to the branches for patch releases.
On Fri, Jul 22, 2016 at 5:42 PM, Huadong Liu (JIRA) wrote:
>
> [
>
The motivation for "dynamic" quota/weights was that we wanted operators to
be able to change these without restarting (all) masters. That means you'd
update these values via operator endpoints, and if you're doing that, then
the flag values become outdated/irrelevant, and we must persist these
Good point. Vinod was working on the endpoints script right next to me, but
I guess he did his pre-release run before I committed Alexander's change.
We'll have to do another run before rc2.
On Mon, Jun 6, 2016 at 5:36 AM, Neil Conway wrote:
> FYI, this commit should have
Firstly, I'm going to take this discussion to dev@, since I think it would
be valuable information for the community and it doesn't contain any
private information.
Secondly, we currently have a simple rule that should be sufficient for
1.0. If an authorization::Action ends in "_WITH_FOO", then
FYI, I made an alternate 1.0 release dashboard with a longer timeframe for
the created vs. resolved chart, and added a couple of my favorite widgets.
Feel free to use anything you find helpful.
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12328256
On Thu, May 26, 2016 at
See also https://issues.apache.org/jira/browse/MESOS-3746
On Wed, May 4, 2016 at 6:13 PM, Benjamin Mahler wrote:
> It's not done atomically. Yes it's possible that only RESERVE succeeded and
> CREATE was dropped due to a failure in the master or agent.
>
> On Wed, May 4,
Sounds great! (although we're short on WebUI maintainers)
Could you file a JIRA at https://issues.apache.org/jira/browse/MESOS
See http://mesos.apache.org/documentation/latest/reporting-a-bug/
On Mon, Apr 11, 2016 at 7:43 AM, haosdent wrote:
> Hi, about "Mesos GUI do not have
"*" is not a standard role, but instead represents unreserved resources
that will be offered to any framework, according to (weighted,
hierarchical) DRF. So it doesn't make sense to talk about the resources
"reserved" for "*". Rather, if you take the total cluster resources, and
subtract the
Haosdent, I think Apache mail may strip out images, so you'll have to send
a link to the QR image.
On Sun, Feb 7, 2016 at 8:02 AM, haosdent wrote:
> Hi, our dear Chinese friends. Because some interesting things related to
> China Network, it is a bit difficult to
You'll need to shorten your commit summary, which is derived from the
'Summary' field in ReviewBoard. You can put a longer description in the
'Description' field, and it will also be included in the final commit
message (although not in the first line, which is restricted to 72 chars).
Also,
Just run `git log` or `git log --oneline` for many more examples. :)
On Thu, Jan 14, 2016 at 11:15 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> You'll need to shorten your commit summary, which is derived from the
> 'Summary' field in ReviewBoard. You can put a longer
Tim/MPark, Note that JIRAs must have their "Fixed Version" set to 0.27.0 to
show up in the generated "Release Notes".
We use "Target Version" to track blockers for the release (and things that
we really really hope will make it in).
On Wed, Jan 13, 2016 at 2:08 PM, Joris Van Remoortere <
I just added AndyPang and chenqiang as Mesos contributors. Now tickets can
be assigned to you.
Did we miss anybody else?
On Wed, Jan 13, 2016 at 1:31 AM, Alex Rukletsov wrote:
> No worries! It's always good to have some buddies in the community.
>
> On Wed, Jan 13, 2016 at
Added. Now JIRAs can be assigned to you.
Thanks for contributing!
On Thu, Jan 7, 2016 at 10:51 AM, Srinivas R Brahmaroutu wrote:
>
> Hi,
>I would like to work on Mesos project and to be able to contribute code
> to the project, please add me as a contributor.
>I
Officially, Apache prefers to distribute source instead of binaries, which
is why Mesosphere volunteered to build and distribute rpm/deb packages as
well as docker images. Apache Mesos could own the Docker files for Mesos
though.
That said, if you have problems with the Mesosphere (or mesoscloud)
Alright, let's revive it. I think we previously had problems trying to
write a multi-master unit test. Might have to do some test infrastructure
work to make that possible.
On Wed, Jan 6, 2016 at 1:14 PM, Neil Conway wrote:
> +1 -- I think we should make this change. The
+1
On Mon, Jan 4, 2016 at 3:19 PM, Joris Van Remoortere <
joris.van.remoort...@gmail.com> wrote:
> +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
Thanks for collecting these! I think the most appropriate place for that
list would be the Apache Mesos Wiki.
Perhaps
https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared+Links
Haosdent, you should have edit permissions if you want to add those design
doc links.
The wiki could
Viktor, you are correct that Mesos' DockerInfo doesn't have explicit
support for the ip:hostPort:containerPort format, but you can use the
DockerInfo.parameters field to pass arbitrary parameters to the docker
CLI.
https://github.com/apache/mesos/blob/0.26.0/include/mesos/mesos.proto#L1482
a) +1 to new cpplint rule for single space after "//"
b) I'd vote for single-space before the comment too. I haven't seen
anybody do double-spaces in Mesos. The only exception to the
single-space rule would be places where we try to align trailing
comments. Not sure if we want to continue to allow
Seems like those tickets need shepherds if we're ever going to land them.
Any volunteers? (I don't have any ppc experience, personally)
On Wed, Dec 16, 2015 at 6:44 AM, Alex Rukletsov wrote:
> Why do you think these tickets are resolved? I see them either in
> reviewable, in
Done. Welcome!
On Tue, Dec 15, 2015 at 9:33 PM, GradyWang wrote:
> Hi,
>
> I've created some JIRA tickets, and want to assign to myself. Can anyone add
> me to the Mesos contributor list?
>
> --
> Regards!
> Grady YQ. Wang
First off, if we're going to have a /reservations endpoint, we should
follow the same PUT+DELETE pattern for reserve+unreserve, instead of
POST+PUT. And we should consider converting /create and /destroy to
PUT+DELETE verbs on a /volumes endpoint.
Secondly, we're going to have to support the
Thanks for the discussion so far. Rereading it has helped me understand the
relationship/overlap between these two proposals. Here are my thoughts.
TL;DR: Let's do both! Not specifying --roles (or ACLs) should mean that any
role can register. Let's also improve the /roles endpoint to
Since it's still a manual process, the website is usually only updated a)
when we have a new release to announce, or b) when some other blog-worthy
content arises (e.g. MesosCon).
On Tue, Nov 10, 2015 at 1:06 AM, Jonathon Rossi wrote:
> It is currently a manual process
+1 Make it so.
On Wed, Nov 4, 2015 at 7:31 AM, haosdent wrote:
> +1 Backticks used in markdown widely.
>
> On Wed, Nov 4, 2015 at 11:03 PM, Bernd Mathiske
> wrote:
>
> > +1
> >
> > > On Nov 2, 2015, at 8:34 PM, Isabel Jimenez <
> >
> we've resolved 134 issues
And committed 325 patches:
$ git log --oneline 0.25.0..HEAD |wc -l
325
On Fri, Nov 6, 2015 at 10:38 AM, Marco Massenzio
wrote:
> I guess that when you're used to trash the opponents scoring 5 goals per
> game, just winning by 2 or 3 goals may
Welcome, Kapil! Well-deserved.
On Thu, Nov 5, 2015 at 2:07 AM, haosdent wrote:
> Congratulations!
>
> On Thu, Nov 5, 2015 at 6:02 PM, Till Toenshoff wrote:
>
>> I'm happy to announce that Kapil Arya has been voted a Mesos committer
>> and PMC member!
>>
>>
to the agenda or ask in IRC and I will relay them for you.
On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF at 3pm
> Pacific tomorrow.
> We will use youtube-onair again, links to be posted to IR
te between
9pm/9am. Let's get these on the calendar officially.
Vinod, are you/Twitter still planning to host the community sync tomorrow?
On Wed, Oct 14, 2015 at 1:01 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> We'll have the next community sync this Thursday (Oct. 15th) fr
e first Thursday". After
>> this, the other meetings (third Thursday, or every other week?) can
>> alternate between 9pm/9am. Let's get these on the calendar officially.
>>
>> Vinod, are you/Twitter still planning to host the community sync
>> tomorrow?
>>
>>
I see 3 docs linked from MESOS-191 (and none in your email), but I assume
you're talking about:
https://docs.google.com/document/d/1syPxygVNEHjG6FoyqslnpUGgNpYKU9QzKBuV2yKmjfQ/edit#heading=h.4fzj9sl24cwy
On Thu, Oct 29, 2015 at 1:00 PM, David Greenberg
wrote:
> Hello
> > +1 for bi-weekly and I have been assuming rotating times in the
> > first
> > > > > place, as I suspect many others as well.
> > > > >
> > > > > (9am and 3pm are not very far apart. Probably better to go for 8am
> > an
Wow, split crowd. Keep in mind that we also want to adjust the times to
better accommodate people in different time zones. This could mean
something like 9am, 3pm, 9pm, 3pm (Pacific). If we do one of these a week,
then we end up with bi-weekly 3pm meetings, for those on the west coast
that don't
gt;
> > On Thu, Oct 1, 2015 at 9:19 AM, haosdent <haosd...@gmail.com> wrote:
> >
> > > Do today have community sync?
> > >
> > > On Fri, Sep 18, 2015 at 12:59 AM, Adam Bordelon <a...@mesosphere.io>
> > > wrote:
> > &g
Added. Now you can assign JIRAs to yourself.
Thanks for contributing!
On Wed, Oct 14, 2015 at 5:29 PM, tommy xiao wrote:
> Hi
> After using Mesos and following Mesos project for quite some time, I would
> like to participate and contribute to the Mesos project. Could I be
er than
> 4M. And our build and check time nearly 40 minutes in travis(Only 1.5
> cores) after use some tricks to speed up. If Mesos code and tests become
> more larger and over 50 minutes in the future, travis also would failed
> because of timeout.
>
> On Sat, Oct 10, 2015 at 2:2
We use Jenkins as our primary post-commit CI infrastructure.
https://builds.apache.org/job/mesos/
The Travis build has been failing ever since it was created, although these
emails may be new. Looks like Travis CI recently upgraded to a
container-based infrastructure.
On Thu, Oct 8, 2015 at 4:19
> personal
> >> glory and the material benefits of a brand new Apple Watch :D
> >>
> >> Congrats to the team that won the MesosCon Europe Hackathon: well
> deserved!
> >>
> >> *Marco Massenzio*
> >>
> >> *Distributed Systems
uld pass. https://travis-ci.org/haosdent/mesos Should I add
> it back to Mesos?
>
> On Fri, Oct 9, 2015 at 5:14 PM, Adam Bordelon <a...@mesosphere.io> wrote:
>
> > We use Jenkins as our primary post-commit CI infrastructure.
> > https://builds.apache.org/job/mesos/
&
Hi Artem, thanks for your work on improving the commit process.
I have used the '-g' feature for github PRs in the past, and we should
continue to support that model, so that new Mesos contributors don't have
to create new RB accounts and learn a new process just for quick
documentation changes,
Hi all,
The vote for Mesos 0.21.2 (rc1) has passed with the following votes.
+1 (Binding)
--
Adam B
Vinod Kone
Michael Park
Niklas Nielsen
There were no 0 or -1 votes.
Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.21.2
It is
Hi all,
The vote for Mesos 0.22.2 (rc1) has passed with the following votes.
+1 (Binding)
--
Adam B
Brenden Matthews
Benjamin Mahler
+1 (Non-binding)
--
haosdent
There were no 0 or -1 votes.
Please find the release at:
p-us.apache.org/repos/asf/mesos.git before.
>
> On Thu, Sep 24, 2015 at 11:29 PM, Adam Bordelon <a...@mesosphere.io>
> wrote:
>
>> I think the github mirror is still behind. It should sync up eventually.
>> You can always pull from Apache git directly too:
>>
Hi friends,
Here's another docker patch release candidate for you! Please vote on
releasing the following candidate as Apache Mesos 0.22.2.
0.22.2 is a bug fix release and includes the following:
* [MESOS-2986] -
+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
On Thu, Sep 24, 2015 at 12:10 AM, Adam Bordelon <a...@mesosphere.io> wrote:
> Hi friends,
>
> Here's another docker patch release candidate for you! Please vote on
> releasing the following candidate as A
you also add a tag 0.22.2-rc1
> <https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.22.2-rc1>
> in
> github?
>
> On Thu, Sep 24, 2015 at 4:50 PM, Adam Bordelon <a...@mesosphere.io> wrote:
>
>> +1 (binding) Tested on CI for CentOS7,
including docker
> tests.
>
> On Wed, Sep 23, 2015 at 10:41 PM, Adam Bordelon <a...@mesosphere.io>
> wrote:
>
> > +1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
> >
> > On Tue, Sep 22, 2015 at 1:41 PM, Niklas Nielsen <nik...@mesosphere.i
es? I see the code under checkPointResource
> is creating a volume path under sandbox. Do these checkpointed resource
> finally get added to Docker:ContainerInfo? If yes, can you point me to that
> location.
>
> Thanks
>
> On Fri, Sep 11, 2015 at 10:35 PM, Adam Bordelo
Hi friends,
Here's a candidate for the last of the docker patch releases
(0.21.x-0.24.x).
Please vote on releasing the following candidate as Apache Mesos 0.21.2.
0.21.2 is a bug fix release and includes the following:
+1 (binding) Tested on CI for CentOS7 and Ubuntu 14.04.
On Thu, Sep 24, 2015 at 5:44 PM, Adam Bordelon <a...@mesosphere.io> wrote:
> Hi friends,
>
> Here's a candidate for the last of the docker patch releases
> (0.21.x-0.24.x).
> Please vote on releasing the following cand
;> +1 (non binding)
> >>
> >> Tested Ubuntu 14.04, OSX
> >>
> >> > On 22 Sep 2015, at 03:06, Adam Bordelon <a...@mesosphere.io> wrote:
> >> >
> >> > Hi friends,
>
Added. Now you can assign JIRAs to yourself.
Welcome to the project! Thanks for contributing
On Tue, Sep 22, 2015 at 7:35 PM, Li Qiang QL Lin wrote:
> Thanks!
>
> Regards
> Liqiang Lin
;> Tested on CI for CentOS5 and CentOS6.
>>
>> On Fri, Sep 18, 2015 at 6:21 PM, Adam Bordelon <a...@mesosphere.io>
>> wrote:
>>
>>> Hi friends,
>>>
>>> Please vote
+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04.
On Wed, Sep 23, 2015 at 10:25 AM, haosdent <haosd...@gmail.com> wrote:
> +1 test on Ubuntu 14.04
>
> On Tue, Sep 22, 2015 at 9:06 AM, Adam Bordelon <a...@mesosphere.io> wrote:
>
>> Hi friends,
Hi friends,
Please vote on releasing the following candidate as Apache Mesos 0.23.1.
0.23.1 is a bug fix release and includes the following:
* [MESOS-2986] - Docker version output is not compatible with Mesos
*
, so I thought I'd
> check back in on this thread.
>
> Thanks,
>
> -- Roger
>
> On Mon, Sep 14, 2015 at 12:33 AM, Adam Bordelon <a...@mesosphere.io>
> wrote:
>
> > Mesos users are having problems using stable Mesos releases with modern
> > Docker due to the
Hi friends,
Please vote on releasing the following candidate as Apache Mesos 0.24.1.
0.24.1 includes the following:
* [MESOS-2986] - Docker version output is not compatible with Mesos
* [MESOS-3136] - COMMAND health
is Van Remoortere <jo...@mesosphere.io>
wrote:
> Youtube on-air: http://youtu.be/ZQT6-fw8Ito
> Speakers channel:
> https://plus.google.com/hangouts/_/hoaevent/AP36tYd59qP_P4ac-NwOI7LztI_hBsku54gXqk1DhFGsKkne_cmByA
>
> On Mon, Sep 14, 2015 at 7:02 PM, Adam Bordelon <a...@mesosph
James, we're certainly interested, but TimSt.Clair, our committer build
expert is relatively inactive lately, so we should find another shepherd. I
trust Cody's build expertise, and he's already given a couple of looks, but
he's not (yet) a committer. Maybe a committer can pair with him to review
> 2015-09-14 18:52 GMT+08:00 Jörg Schad <jo...@mesosphere.io>:
>
> > Lgtm, thanks for taking care of this!
> >
> > On Mon, Sep 14, 2015 at 9:33 AM, Adam Bordelon <a...@mesosphere.io>
> wrote:
> >
> > > Mesos users are having problems usin
I'm on it.
On Mon, Sep 14, 2015 at 11:14 PM, Qian AZ Zhang wrote:
>
> Hi all,
>
> Is anyone willing to shepherd on MESOS-3408? Thanks!
>
>
> Regards,
> Qian Zhang
r: The Mesos Community Developer Sync will be happening today at
>>> 3pm Pacific.
>>>
>>> To participate remotely, join the Google hangout:
>>> https://plus.google.com/hangouts/_/twitter.com/mesos-sync
>>>
>>> On Thu, Jun 18, 2015 at 7:22 AM,
Mesos users are having problems using stable Mesos releases with modern
Docker due to the change in version strings in Docker 1.8 (also in Fedora
22) as described in https://issues.apache.org/jira/browse/MESOS-2986. There
have been requests for patch releases ranging from 0.21.x to 0.24.x. I
would
Hi Jincheng,
You have been added as a contributor, and may now assign issues to yourself.
Welcome to the community!
-Adam-
On Sun, Aug 23, 2015 at 9:28 AM, Jincheng Li jcli@gmail.com wrote:
Hi all,
I've been following the Mesos project for a bit and would like to
contribute. Could I be
id.apache and our SVN repo containing KEYS.
Do I need to do anything specific for maven?
On Tue, Aug 18, 2015 at 1:25 PM, Adam Bordelon a...@mesosphere.io wrote:
Haven't seen that one. Are you sure you've got your gpg key properly set
up
with Maven?
On Tue, Aug 18, 2015 at 1:13 PM, Vinod
to be in 0.24.0 please land them by EOW.
Thanks,
On Tue, Jul 21, 2015 at 4:10 PM, Adam Bordelon
a...@mesosphere.io
wrote:
Thanks, Vinod.
I've got a handful of JIRAs I'd really like to see land in
0.24.0.
https://issues.apache.org/jira/browse/MESOS-2559 Do not use
I get the Rakefile?
On Thu, Jul 30, 2015 at 6:12 AM, Ajay Krishna ajaykrish...@gmail.com
wrote:
Hi Adam,
That solution looks clean and generic. Thanks for pointing to those
issues.
On Thu, Jul 30, 2015 at 3:06 AM, Adam Bordelon a...@mesosphere.io
wrote:
Hi Ajay
Hi Ajay,
This broken link is already tracked in
https://issues.apache.org/jira/browse/MESOS-1521 and
https://issues.apache.org/jira/browse/MESOS-2004
This one may be tricky due to how our Rakefile translates the .md docs into
static html.
On Wed, Jul 29, 2015 at 2:20 PM, Ajay Krishna
Hi Diana,
Sorry for the slow response. We're still in the design phase of this (epic)
feature. BenH was preparing a proposal, but I haven't seen him post it yet.
Once we have agreement on the proposal, and a design doc that details which
new endpoints/messages/etc. we'll need, we can create JIRA
...
Thanks Adam.
On Fri, Jul 17, 2015 at 4:42 PM Adam Bordelon a...@mesosphere.io
wrote:
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following
From your pastebin, it looks like maven ran out of memory, either while
compiling or while generating javadoc.
After you give mvn more memory, it tries to javadoc the class files instead
of just java files. Weird. Do you have abnormal mvn/java settings? Let's
file a JIRA.
I'm glad you found a
Thanks, Vinod.
I've got a handful of JIRAs I'd really like to see land in 0.24.0.
https://issues.apache.org/jira/browse/MESOS-2559 Do not use
RunTaskMessage.framework_id.
https://issues.apache.org/jira/browse/MESOS-2600 Add /reserve and
/unreserve endpoints on the master for dynamic reservation
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
1 - 100 of 220 matches
Mail list logo