Re: Convention for Backward Compatibility for New Operations in Mesos 1.6

I think we should definitely do option 2 regardless of whether we do option 1 as well, since although in this case it will still crash 1.5.0, at least in the future we won't have to have this worry again. On 4/16/18, 2:04 PM, "Chun-Hung Hsiao" wrote: Hi all, As some might have al

Re: Easing the Pain of Code Formatting in Mesos

I regret I have but one +1 to give, etc. > On Jun 14, 2017, at 7:32 PM, Michael Park wrote: > > I'm increasingly hearing that many contributors who want to contribute to > Mesos find that > it's often difficult to do so. One of the big issues is due to our > formatting rules which is not > autom

Re: Question about the deprecated policy after 1.0

not a change appears to be ‘minor’ under some rubric (and I agree that this change could seem minor), if it’s part of the v1 mesos.proto, it affects downstream users (such as me, a writer of schedulers). > On Tue, Sep 6, 2016 at 1:18 PM, Silas Snider <mailto:swsni...@apple.com>> wro

Re: Question about the deprecated policy after 1.0

There’s a little history to this: In https://reviews.apache.org/r/50812/ , on the 8th of August, the HTTP health check message was changed to be entirely incompatible with the previous HTTP health check message. Not only was its name changed (breaking compat