Re: [openstack-dev] [all] versioning the api-ref?

2016-08-26 Thread Anne Gentle
l > > > > -Original Message- > > From: Sean Dague [mailto:s...@dague.net] > > Sent: Thursday, August 18, 2016 10:20 AM > > To: Nikhil Komawar <nik.koma...@gmail.com>; OpenStack Development > Mailing List (not for usage questions) <openstack-dev@lists

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-26 Thread Bashmakov, Alexander
mages-parameters.yaml > > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Thursday, August 18, 2016 10:20 AM > To: Nikhil Komawar <nik.koma...@gmail.com>; OpenStack Development Mailing > List (not for usage questions) <openstack-dev@lists.openstack.org&

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-18 Thread Bashmakov, Alexander
oma...@gmail.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [all] versioning the api-ref? On 08/18/2016 11:57 AM, Nikhil Komawar wrote: > I guess the intent was to indicate the need for indicating the micr

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-18 Thread Sean Dague
On 08/18/2016 11:57 AM, Nikhil Komawar wrote: > I guess the intent was to indicate the need for indicating the micro or > in case of Glance minor version bump when required. > > The API isn't drastically different, there are new and old elements as > shown in the Nova api ref linked. Right, so

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-18 Thread Nikhil Komawar
I guess the intent was to indicate the need for indicating the micro or in case of Glance minor version bump when required. The API isn't drastically different, there are new and old elements as shown in the Nova api ref linked. On 8/12/16 5:49 AM, Sean Dague wrote: > On 08/11/2016 06:02 PM,

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-12 Thread Andreas Jaeger
On 08/12/2016 01:43 PM, Jim Rollenhagen wrote: > On Thu, Aug 11, 2016 at 6:13 PM, John Dickinson wrote: >> >> >> On 11 Aug 2016, at 15:02, Brian Rosmaita wrote: >> >>> I have a question about the api-ref. Right now, for example, the new >>> images v1/v2 api-refs are accurate for

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-12 Thread Jim Rollenhagen
On Thu, Aug 11, 2016 at 6:13 PM, John Dickinson wrote: > > > On 11 Aug 2016, at 15:02, Brian Rosmaita wrote: > >> I have a question about the api-ref. Right now, for example, the new >> images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are >> being generated as we

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-12 Thread Sean Dague
On 08/11/2016 06:02 PM, Brian Rosmaita wrote: > I have a question about the api-ref. Right now, for example, the new > images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are > being generated as we speak for changes in master that won't be > available to consumers until Newton is

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-11 Thread John Dickinson
On 11 Aug 2016, at 15:02, Brian Rosmaita wrote: > I have a question about the api-ref. Right now, for example, the new > images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are > being generated as we speak for changes in master that won't be > available to consumers until Newton

[openstack-dev] [all] versioning the api-ref?

2016-08-11 Thread Brian Rosmaita
I have a question about the api-ref. Right now, for example, the new images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are being generated as we speak for changes in master that won't be available to consumers until Newton is released (unless they build from source). If those bug