Re: http://mesos.apache.org/downloads/ is not up to date

Thanks for pointing this out Adam, I've added mpark who is the release manager for 1.3.2. On Tue, Feb 6, 2018 at 6:12 AM, Adam Cecile wrote: > Hi guys, > > > Did you notice Mesos 1.3.2 is missing from the official download page ? > > http://mesos.apache.org/downloads/ > >

Reminder: Design Doc for Mesos CLI Re-design

I've heard a lot of interest in there being investment in the mesos CLI. For those that are interested, please take a look at the re-design doc and share your feedback: https://docs.google.com/document/d/1r6Iv4Efu8v8IBrcUTjgYkvZ32WVsc gYqrD07OyIglsA/edit Feel free to make comments in the doc,

Re: Looking for shepherd

In case others also look at this thinking this still needs a shepherd, this has been committed. On Mon, Feb 12, 2018 at 6:39 AM, Tomek Janiszewski wrote: > I need someone to review and merge this change > https://reviews.apache.org/r/65569/ > It should fix ARM tests. >

Re: [VOTE] C++14 Upgrade

> I guess we need to test out whether running Mesos built with newer version > of gcc (also glibc) on older version of distro is safe. Is it possible to install the newer gcc / glibc on Jessie? It seems there are some comments on the spreadsheet that say the method posted is not safe? What about

Re: [VOTE] C++14 Upgrade

On Mon, Feb 12, 2018 at 1:22 PM, Zhitao Li wrote: > On Mon, Feb 12, 2018 at 11:58 AM, Michael Park wrote: > > > On Mon, Feb 12, 2018 at 10:32 AM, Zhitao Li > wrote: > > > > > Will there be a deprecation cycle for the proposed

Re: [VOTE] C++14 Upgrade

On Mon, Feb 12, 2018 at 11:58 AM, Michael Park wrote: > On Mon, Feb 12, 2018 at 10:32 AM, Zhitao Li wrote: > > > Will there be a deprecation cycle for the proposed change? > > > There is no deprecation cycle for the proposed change. > I take that the

[GitHub] mesos pull request #264: WIP: docker image build automation

Github user bbannier closed the pull request at: https://github.com/apache/mesos/pull/264 ---

[GitHub] mesos pull request #264: WIP: docker image build automation

GitHub user bbannier opened a pull request: https://github.com/apache/mesos/pull/264 WIP: docker image build automation You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbannier/mesos t/docker_image_build Alternatively you can

Re: [VOTE] C++14 Upgrade

On Mon, Feb 12, 2018 at 10:32 AM, Zhitao Li wrote: > Will there be a deprecation cycle for the proposed change? There is no deprecation cycle for the proposed change. > Our org still uses Debian Jessie and we do not see ourselves off that > before EOY. > This is

Re: [VOTE] C++14 Upgrade

Will there be a deprecation cycle for the proposed change? Our org still uses Debian Jessie and we do not see ourselves off that before EOY. On Mon, Feb 12, 2018 at 8:38 AM, James Peach wrote: > > > > On Feb 11, 2018, at 10:33 PM, Michael Park wrote: > > >

Re: [VOTE] C++14 Upgrade

> On Feb 11, 2018, at 10:33 PM, Michael Park wrote: > > On Sun, Feb 11, 2018 at 6:00 PM James Peach wrote: > >> >> >>> On Feb 9, 2018, at 9:28 PM, Michael Park wrote: >>> >>> I'm going to put this up for a vote. My plan is to bump

Re: Introducing `support/mesos-build.sh`

How can I use it for our ARM CI? JOBS=16 OS=arm64v8/ubuntu:16.04 ./support/mesos-build.sh + set -e + set -o pipefail + : arm64v8/ubuntu:16.04 + : autotools + : gcc + : '--verbose --disable-libtool-wrappers' + : 'GLOG_v=1 MESOS_VERBOSE=1' + : 16 ++ git rev-parse --show-toplevel +

Looking for shepherd

I need someone to review and merge this change https://reviews.apache.org/r/65569/ It should fix ARM tests.

Re: [VOTE] C++14 Upgrade

+1. I believe the spreadsheet linked in MESOS-7949 makes it pretty clear that the benefits outweigh the required build requirement changes. > On Feb 10, 2018, at 6:28 AM, Michael Park wrote: > > I'm going to put this up for a vote. My plan is to bump us to C++14 on Feb >

Re: Soliciting Hackathon Ideas

Judith — we have newbie and newbie++ labels [1]. To help people land their changes at the end of a hackathon, we should find shepherds for issues before giving them out to folks. Shepherds should have time for reviews and an idea about the approach. [1]

Re: [VOTE] C++14 Upgrade

+1 (binding) Mesos codebase seems to be ready for the upgrade (tested on Mesosphere's internal CI). I think beginning of 2018 is the right time for this. In addition to technical reasons mentioned by MPark, I add one more: modernising the codebase fosters learning, fun, and makes it a more