I should have added that it will be inconvenient for us but not impossible
to cope. However I am not convinced about the need to rename so let's chat
about this on the review or the dev list.

---
Jiang Yan Xu <y...@jxu.me> | @xujyan <https://twitter.com/xujyan>

On Wed, May 24, 2017 at 10:29 AM, Yan Xu <y...@jxu.me> wrote:

> I made a comment on https://reviews.apache.org/r/59453/
>
> ---
> Jiang Yan Xu <y...@jxu.me> | @xujyan <https://twitter.com/xujyan>
>
> On Wed, May 24, 2017 at 9:48 AM, Vinod Kone <vi...@mesosphere.io> wrote:
>
>> If it hasn't been released it should be ok for us to do the rename. There
>> are no backwards compatible guarantees for such things. But a heads up is
>> always nice, so thanks for doing that.
>>
>> On Wed, May 24, 2017 at 12:44 PM, Neil Conway <neil.con...@gmail.com>
>> wrote:
>>
>>> FYI, I merged the change to rename this field into the master and
>>> 1.3.x branches; it will be included in the next 1.3.0 release
>>> candidate.
>>>
>>> Neil
>>>
>>>
>>> On Mon, May 22, 2017 at 10:43 AM, Alexander Rojas
>>> <alexan...@mesosphere.io> wrote:
>>> > Hey guys,
>>> >
>>> > We just noted that there was an error when the `RegisterAgent` act was
>>> > introduced. Namely, its object field is listed as `agent` when by
>>> convention
>>> > we have used plural, so it should be `agents`. This ACL hasn’t been
>>> part of
>>> > any released version of Mesos, so if no one is using it I will try to
>>> push
>>> > for a rename without going through any deprecation cycle.
>>> >
>>> > The big question is if any of you are using this particular ACL in
>>> > production right now?
>>> >
>>> > Alexander Rojas
>>> > alexan...@mesosphere.io
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>

Reply via email to