On Tue, 04 Mar 2014 12:10:15 -0500 Russell Bryant <[email protected]> wrote: > > What I'd like to do next is work through a new proposal that includes > keeping both v2 and v3, but with a new added focus of minimizing the > cost. This should include a path away from the dual code bases and to > something like the "v2.1" proposal.
That sounds good to me. I would be very interested in any feedback that people have around the concept of v2.1 that looks just like v2 but has strong input validation. So that would be the only backwards incompatible change and would only affect those who are currently misusing the API. Because we are not modifying the original V2 API code people could do side by side tests with real clients to see how badly in practice an individual bit of software is. And we'll have tempest tests to verify the correct input behaviour path for V2 remains the same. In the meantime we'll aim to get some more fleshed out POC code out for the decorator approach to implementing V2 on the V3 codebase that we can show at the design summit. Chris _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
