Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

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 minimum glibc version/linux distro releases etc we support but currently we don't and there are folks who use Mesos that depend on this version. We should

Re: [VOTE] Release Apache Mesos 1.1.2 (rc1)

I saw this on ASF CI

Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

s/0.13.0/1.3.0/ :) --- Jiang Yan Xu | @xujyan On Mon, May 8, 2017 at 3:45 PM, Yan Xu wrote: > I am still hoping that we get https://issues.apache.org/ > jira/browse/MESOS-7378 fixed before shipping 0.13.0. :) > > --- > Jiang Yan Xu

Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

Personally, I'm not convinced that we need to fix MESOS-7378. The problem is essentially a bug in glibc that was fixed 6 years ago. (As a point of reference, the oldest version of g++ we support was released 2 years ago... :) ) Neil On Mon, May 8, 2017 at 3:45 PM, Yan Xu wrote: > I

Re: [VOTE] Release Apache Mesos 1.3.0 (rc1)

I am still hoping that we get https://issues.apache.org/jira/browse/MESOS-7378 fixed before shipping 0.13.0. :) --- Jiang Yan Xu | @xujyan On Fri, May 5, 2017 at 6:31 PM, Michael Park wrote: > Hi all, > > Please vote on releasing the

Version numbers in Mesos

I would like to make a few changes to how Mesos handles version numbers: (1) Mesos versions (e.g., as defined in `configure.ac`) must be parseable as valid SemVer (see http://semver.org/). This has always been the case with version numbers assigned by the Apache Mesos project, but if your