Open Stack

On Mon, 05 Jan 2015 11:10:41 -0500
Jay Pipes <jaypipes at gmail.com> wrote:

> >
> > Thoughts on getting consistency across all 3 projects (and possibly
> > others)?
> 
> Yeah, I personally like the second option as well, but agree that 
> consistency is the key (pun intended) here.
> 
> I would say let's make a decision on the standard to go with
> (possibly via the API or SDK working groups?) and then move forward
> with support for that option in all three clients (and continue to
> support the old behaviour for 2 release cycles, with deprecation
> markings as appropriate).

+1 to making this available in a consistent way. We need need to support
the old client behaviour for at least a couple of cycles (maybe a bit
longer) and the burden of doing so is pretty low. I don't think however
that we can drop the REST API behaviour that quickly. 2 cycles for API
deprecation in the past has been considered an insufficent length of
time because of app breakage

Regards,

Chris