2015-06-04 23:27 GMT+08:00 Lucas Alvares Gomes :
> Hi Ruby,
>
> Thanks for starting this thread, just like you I've been always
> confused about when and when not bump the microversioning of the API.
>
> > Backwards compatible API adds with no user signaling is a fallacy
> > because it assumes the
2015-06-05 5:35 GMT+08:00 Devananda van der Veen :
>
> On Jun 4, 2015 11:11 AM, "Chris Friesen"
> wrote:
> >
> > On 06/04/2015 10:14 AM, Devananda van der Veen wrote:
> >>
> >>
> >> On Jun 4, 2015 8:57 AM, "Monty Taylor" >
> >
> >> > So, seriously - let's grow up and start telling people that t
On 06/04/2015 05:27 PM, Lucas Alvares Gomes wrote:
Hi Ruby,
Thanks for starting this thread, just like you I've been always
confused about when and when not bump the microversioning of the API.
Backwards compatible API adds with no user signaling is a fallacy
because it assumes the arrow of ti
On Jun 4, 2015 11:11 AM, "Chris Friesen"
wrote:
>
> On 06/04/2015 10:14 AM, Devananda van der Veen wrote:
>>
>>
>> On Jun 4, 2015 8:57 AM, "Monty Taylor"
>
>> > So, seriously - let's grow up and start telling people that they do
not
>> > get to pick and choose user-visible feature sets. If they
On 06/04/2015 10:14 AM, Devananda van der Veen wrote:
On Jun 4, 2015 8:57 AM, "Monty Taylor"
> So, seriously - let's grow up and start telling people that they do not
> get to pick and choose user-visible feature sets. If they have an unholy
> obsession with a particular backend technology
So we should have told the folks to so developing agent? (Not sure why you
all think I'm talking about us) Maybe.
But anyway anyone deliberately ignores my points, so I'm done with this
discussion.
04 июня 2015 г. 18:17 пользователь "Devananda van der Veen" <
devananda@gmail.com> написал:
>
>
On Jun 4, 2015 8:57 AM, "Monty Taylor" wrote:
>
> On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
> > On 06/04/2015 05:03 PM, Sean Dague wrote:
> >> On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
> >>> On 06/04/2015 04:40 PM, Ruby Loo wrote:
> Hi,
>
> In Kilo, we introduced microversio
On 06/04/2015 05:43 PM, Sean Dague wrote:
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
On 06/04/2015 05:03 PM, Sean Dague wrote:
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progre
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
> On 06/04/2015 05:03 PM, Sean Dague wrote:
>> On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
>>> On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effo
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote:
> On 06/04/2015 05:03 PM, Sean Dague wrote:
>> On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
>>> On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effo
On 06/04/2015 05:03 PM, Sean Dague wrote:
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effort now to add microversion into the
API-WG's guidelines, to provide a
Hi Ruby,
Thanks for starting this thread, just like you I've been always
confused about when and when not bump the microversioning of the API.
> Backwards compatible API adds with no user signaling is a fallacy
> because it assumes the arrow of time flows only one way.
>
> If at version 1.5 you h
On 06/04/2015 10:50 AM, Dmitry Tantsur wrote:
> On 06/04/2015 04:40 PM, Ruby Loo wrote:
>> Hi,
>>
>> In Kilo, we introduced microversions but it seems to be a
>> work-in-progress. There is an effort now to add microversion into the
>> API-WG's guidelines, to provide a consistent way of using microv
On 06/04/2015 04:40 PM, Ruby Loo wrote:
Hi,
In Kilo, we introduced microversions but it seems to be a
work-in-progress. There is an effort now to add microversion into the
API-WG's guidelines, to provide a consistent way of using microversions
across OpenStack projects [1]. Specifically, in the
Hi,
In Kilo, we introduced microversions but it seems to be a work-in-progress.
There is an effort now to add microversion into the API-WG's guidelines, to
provide a consistent way of using microversions across OpenStack projects
[1]. Specifically, in the context of this email, there is a proposed
15 matches
Mail list logo
