[
https://issues.apache.org/jira/browse/MESOS-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382562#comment-14382562
]
Benjamin Mahler commented on MESOS-2558:
----------------------------------------
:)
I've found these kind of phased changes to be really hard to follow through on
unless we have tickets with the appropriate target versions and treat them as
"blocking" the release if not taken care of. Are you planning to update this
ticket as things progress, or pull out some subtasks for each version?
> Mark RunTaskMessage.framework_id as optional
> --------------------------------------------
>
> Key: MESOS-2558
> URL: https://issues.apache.org/jira/browse/MESOS-2558
> Project: Mesos
> Issue Type: Technical task
> Components: framework
> Reporter: Kapil Arya
> Assignee: Kapil Arya
>
> In this release (N), we would still keep setting it (handles older Slaves
> with newer Master). Add code to handle it being unset in the Slave (handles
> older Master with newer Slaves).
> In the following release (N+1), stop reading/setting it (the previous version
> would handle the unset case).
> In release N+2, remove the field altogether (the previous release is not
> setting/reading it).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
