Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-25 Thread Sean Dague
On 01/25/2017 06:16 AM, Monty Taylor wrote: I have quibble with the current microversions construct. It's mostly semantic in nature, and I _think_ it's not valid/useful - but I'm going to describe it here just so that I've said it and we can all acknowledge it and move on. My concern is with

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-25 Thread Monty Taylor
On 01/25/2017 09:16 AM, Monty Taylor wrote: > On 01/24/2017 12:39 PM, Chris Dent wrote: >> On Mon, 23 Jan 2017, Sean Dague wrote: >> >>> We all inherited a bunch of odd and poorly defined behaviors in the >>> system we're using. They were made because at the time they seemed like >>> reasonable

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-25 Thread Monty Taylor
On 01/24/2017 12:39 PM, Chris Dent wrote: > On Mon, 23 Jan 2017, Sean Dague wrote: > >> We all inherited a bunch of odd and poorly defined behaviors in the >> system we're using. They were made because at the time they seemed like >> reasonable tradeoffs, and a couple of years later we learned

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-25 Thread Chris Dent
On Wed, 25 Jan 2017, Thierry Carrez wrote: We were discussing this in the context of an "assert" tag, not a goal. Yes, but it is often the case that changes are being evaluated as if it was a goal. A couple of glance related changes experienced reactions of "this doesn't meet compatibility

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-25 Thread Thierry Carrez
Chris Dent wrote: > [...] > That could very well be fine, but we have evidence that: > > * some projects don't yet use microversions in their APIs > * some projects have no intention of using microversions or at least > have internal conflict about doing so > * some projects would like to

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-24 Thread Chris Dent
On Mon, 23 Jan 2017, Sean Dague wrote: We all inherited a bunch of odd and poorly defined behaviors in the system we're using. They were made because at the time they seemed like reasonable tradeoffs, and a couple of years later we learned more, or needed to address a different use case that

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-23 Thread Sean Dague
On 01/23/2017 08:11 AM, Chris Dent wrote: > On Wed, 18 Jan 2017, Chris Dent wrote: > >> The review starts with the original text. The hope is that >> commentary here in this thread and on the review will eventually >> lead to the best document. > > https://review.openstack.org/#/c/421846 >

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

2017-01-23 Thread Chris Dent
On Wed, 18 Jan 2017, Chris Dent wrote: The review starts with the original text. The hope is that commentary here in this thread and on the review will eventually lead to the best document. https://review.openstack.org/#/c/421846 There's been a bit of commentary on the review which I'll