[
https://issues.apache.org/jira/browse/MESOS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone 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:
-Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
-Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
-Executor Restart
Maybe not _breaking_:
-Adding timestamps to Tasks / Status Updates.
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
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:
> -Making Resources First-Class (i.e. cpus, mem, disk, network, etc).
> -Adding cpu Resource types, e.g. {SOFT, HARD, PINNED}
> -Executor Restart
> Maybe not _breaking_:
> -Adding timestamps to Tasks / Status Updates.
--
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
