Excerpts from Matt Riedemann's message of 2018-05-17 17:23:09 -0500:
> On 5/17/2018 11:02 AM, Doug Hellmann wrote:
> > After some discussion on twitter and IRC, we've added a new session to
> > the Forum schedule for next week to discuss our options for cleaning up
> > some of the design/technical debt in our REST APIs.
> Not to troll too hard here, but it's kind of frustrating to see that 
> twitter trumps people actually proposing sessions on time and then 
> having them be rejected.
> > The session description:
> > 
> >    The introduction of microversions in OpenStack APIs added a
> >    mechanism to incrementally change APIs without breaking users.
> >    We're now at the point where people would like to start making
> >    old things go away, which means we need to hammer out a plan and
> >    potentially put it forward as a community goal.
> > 
> > [1]https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21881/api-debt-cleanup
> This also came up at the Pike PTG in Atlanta:
> https://etherpad.openstack.org/p/ptg-architecture-workgroup
> See the "raising the minimum microversion" section. The TODO was Ironic 
> was going to go off and do this and see how much people freaked out. 
> What's changed since then besides that not happening? Since I'm not on 
> twitter, I don't know what new thing prompted this.

What changed is that we thought doing it as a coordinated effort,
rather than one team, would work better, because we wouldn't have
a team appearing to be an outlier in terms of their API support
"guarantees".  We also wanted to start the planning early, so that
teams could talk about it at the PTG and make more detailed plans
for the changes over the course of Stein, to be implemented in the
next cycle (assuming we all decide that's the right timing).

The only aspect of this that's settled today is that we want to
talk about it. Each team will still need to consider whether, and
how, to do it.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to