aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <>
Subject [jira] [Resolved] (AURORA-1503) Determine how best to keep up with Mesos releases
Date Sun, 25 Oct 2015 04:01:27 GMT


Zameer Manji resolved AURORA-1503.
    Resolution: Fixed

Based on the discussion here and on the mailing list. I will be releasing 0.10.0 from master
and then bumping the dependency to 0.24 for 0.11.0.

> Determine how best to keep up with Mesos releases
> -------------------------------------------------
>                 Key: AURORA-1503
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
> Aurora 0.9.0 was released with a dependency on Mesos 0.22. The current release is Mesos
0.24. There was a change with how data was published into the Mesos ZK node in Mesos 0.23
(Protobuf to JSON) meaning that frameworks that are linked against 0.22 will get a libmesos
error when using the 0.24 library.
> The task is to determine what is the best way forward in scenarios like this. Possible
options include:
> * Release 0.9.x with a newer mesos dependency
> * Cut a new release from master that depends on 0.24
> Problems include backwards/forwards compatibility. For example if we release 0.9.1 with
a dependency on Mesos 0.24 will Aurora still work against a Mesos Master that runs 0.22?

This message was sent by Atlassian JIRA

View raw message