On Thu, Apr 24, 2014 at 9:31 AM, Connor Doyle email@example.com wrote:
There is some incompatibility, due to the fact that Mesos 0.16.x and below depend upon protobuf 2.4.2, while Mesos 0.17.x and above depend upon protobuf 2.5.0. The current stable release of Marathon (0.4.1) pre-dates Mesos 0.17.0. Our current plan for the next Marathon release (which will be 0.5.0, scheduled for next week) is to offer a package compatible with Mesos 0.16.x and below, and another package for the more recent and future Mesos releases. This is all a bit complicated, so we will be sure to explain the situation clearly in the release notes. At the same time, we think it’s important that current Marathon users are able to take advantage of the new features and bug fixes in the 0.5.x series without having to upgrade Mesos.
On 24 April 2014 at 08:38:09, Cory Watson (firstname.lastname@example.org) wrote:
> Last time I updated Mesos I ran into incompatibilities between Mesos &
> Marathon. Is there some sort of matrix of pairings that are legit?
> Looks like the Marathon tutorial points to Marathon 0.4.0 and the Mesos
> downloads points to 0.18.0. I'm afraid to upgrade however because I
> believe that version of Marathon doesn't jive with Mesos 0.18.0.
> Cory Watson
> Principal Infrastructure Engineer // Keen IO