----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51803/#review148536 -----------------------------------------------------------
include/mesos/mesos.proto (line 372) <https://reviews.apache.org/r/51803/#comment215982> In genenal I think we should state "Feature X will be deprecated in version Y in favor of feature Z" to help folks understand the reasoning. In this case there happens to be difference of opinions on whether this feature/field should be deprecated in 2.0 (which we can discuss outside this review) but could you at least in this review add why this is deprecated and what do you recommend people to do when it is deprecated? - Jiang Yan Xu On Sept. 12, 2016, 7 a.m., haosdent huang wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/51803/ > ----------------------------------------------------------- > > (Updated Sept. 12, 2016, 7 a.m.) > > > Review request for mesos, Alexander Rukletsov, Joseph Wu, Silas Snider, and > Jiang Yan Xu. > > > Bugs: MESOS-6110 > https://issues.apache.org/jira/browse/MESOS-6110 > > > Repository: mesos > > > Description > ------- > > Ensured `HealthCheck::HTTPCheckInfo` compatible with the old one. > > > Diffs > ----- > > include/mesos/mesos.proto eb61b6243202464da2307d06d80700f19f9c25d4 > include/mesos/v1/mesos.proto 62231522f4bfddfc6c440a299dd01080cbe25f6a > > Diff: https://reviews.apache.org/r/51803/diff/ > > > Testing > ------- > > > Thanks, > > haosdent huang > >