Open Stack

On 06/17/2015 03:35 AM, Ken'ichi Ohmichi wrote:
> 2015-06-16 21:16 GMT+09:00 Jay Pipes <jaypipes at gmail.com>:
>> On 06/16/2015 08:00 AM, Dmitry Tantsur wrote:
>>>
>>>
>>> 16 июня 2015 г. 13:52 пользователь "Jay Pipes" <jaypipes at gmail.com
>>> <mailto:jaypipes at gmail.com>> написал:
>>>   >
>>>   > On 06/16/2015 04:36 AM, Alex Xu wrote:
>>>   >>
>>>   >> So if our min_version is 2.1 and the max_version is 2.50. That means
>>>   >> alternative implementations need implement all the 50 versions
>>>   >> api...that sounds pain...
>>>   >
>>>   >
>>>   > Yes, it's pain, but it's no different than someone who is following
>>> the Amazon EC2 API, which cuts releases at a regular (sometimes every
>>> 2-3 weeks) clip.
>>>   >
>>>   > In Amazon-land, the releases are date-based, instead of
>>> microversion/incrementing version-based, but the idea is essentially the
>>> same.
>>>   >
>>>   > There is GREAT value to having an API mean ONE thing and ONE thing
>>> only. It means that developers can code against something that isn't
>>> like quicksand -- constantly changing meanings.
>>>
>>> Being one of such developers, I only see this "value" for breaking
>>> changes.
>>
>>
>> Sorry, Dmitry, I'm not quite following you. Could you elaborate on what you
>> mean by above?
>
> I guess maybe he is thinking the value of microversions is just for
> backwards incompatible changes and backwards compatible changes are
> unnecessary to be managed by microversions because he is proposing it
> as Ironic patch.

Exactly. That's not only my thinking, that's my experience from Kilo as 
both Ironic developer, and developer *for* Ironic (i.e. the very person 
you're trying to make happy).

>
> Thanks
> Ken Ohmichi
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>