You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/03/03 02:27:12 UTC
[jira] [Updated] (MESOS-338) Pre 1.0.0 Breaking Changes.
[ https://issues.apache.org/jira/browse/MESOS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler updated MESOS-338:
----------------------------------
Description:
This is to establish a list of pre-1.0.0 release breaking changes we'd like to get in:
Definitely:
-Slave Recovery: MESOS-110
-Resource Monitoring: MESOS-324
Others:
-Executor Restart
-Using protobuf -> JSON conversion: MESOS-269
Maybe not _breaking_:
-Adding timestamps to Tasks / Status Updates.
-Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
-Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
was:
This is to establish a list of pre-1.0.0 release breaking changes we'd like to get in:
Definitely:
-Slave Recovery: MESOS-110
-Resource Monitoring: MESOS-324
Others:
-Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
-Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
-Executor Restart
-Using protobuf -> JSON conversion: MESOS-269
Maybe not _breaking_:
-Adding timestamps to Tasks / Status Updates.
> Pre 1.0.0 Breaking Changes.
> ---------------------------
>
> Key: MESOS-338
> URL: https://issues.apache.org/jira/browse/MESOS-338
> Project: Mesos
> Issue Type: Brainstorming
> Reporter: Benjamin Mahler
> Priority: Critical
>
> This is to establish a list of pre-1.0.0 release breaking changes we'd like to get in:
> Definitely:
> -Slave Recovery: MESOS-110
> -Resource Monitoring: MESOS-324
>
> Others:
> -Executor Restart
> -Using protobuf -> JSON conversion: MESOS-269
> Maybe not _breaking_:
> -Adding timestamps to Tasks / Status Updates.
> -Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
> -Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira