+1 For the sum up. Now it is clear for me.
On Sat, Oct 29, 2016 at 6:45 AM, Vinod Kone wrote:
> We had an extended discussion around this in the last community sync.
> Thanks for those who participated!
>
> To sum up the discussion:
>
> --> As mesos devs, we should strive to not make incompatibl
We had an extended discussion around this in the last community sync.
Thanks for those who participated!
To sum up the discussion:
--> As mesos devs, we should strive to not make incompatible changes in
APIs, flags, environment variables.
--> In the rare case where an incompatible change is pref
Thanks @yan's great inputs! I couldn't agree more almost of them.
> Also the API is not just what the machine reads but all the documentation
associated with it, right? It depends on what the documentation says; what
the user _should_ expect.
I think different users may have different expectation
We will chat about this in the upcoming community sync (thursday 3 PM). So,
please make sure to attend if you are interested.
On Fri, Oct 14, 2016 at 3:44 PM, Yan Xu wrote:
>
> On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote:
>
>> Thanks Alex for starting this!
>>
>> In addition to comments below
On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote:
> Thanks Alex for starting this!
>
> In addition to comments below, I think it'll be helpful to keep the
> existing versioning doc concise and user-friendly while having a dedicated
> doc for the "implementation details" where precise requirements an
Thanks Alex for starting this!
In addition to comments below, I think it'll be helpful to keep the
existing versioning doc concise and user-friendly while having a dedicated
doc for the "implementation details" where precise requirements and
procedures go. Maybe some duplication/cross-referencing
>How about splitting the unnamed version into explicit v0, v2, and internal?
Currently our internal protobuf and v0 protobuf use the same unnamed
version protobuf and under the same namespace (`package mesos`).
If we are going to split v0 and internal, that requires copy all protobuf
files under `
Folks,
There have been a bunch of online [1, 2] and offline discussions about our
deprecation and versioning policy. I found that people—including
myself—read the versioning doc [3] differently; moreover some aspects are
not captured there. I would like to start a discussion around this topic by
s
8 matches
Mail list logo