Open Stack

On 07/25/2012 04:41 PM, Mark McLoughlin wrote:
>>>      - I hate to think of us rejecting API fixes with "this needs to wait
>>>        until v3" and then, when v3 comes around, we don't actually get
>>>        around to fixing those issues. We need some way of channelling
>>>        people's desire to fix the API, even if that's just helping to
>>>        document what needs fixing in v3.
>>
>> Agreed. Is there some kind of artifact in launchpad that we can track to?
>
> Not that I know of. How could we do this? A v3-api blueprint with most
> of the details in a wiki page? And also a v3-api tag for bugs which
> we're deferring until v3?

Given that launchpad lets us target a change against multiple projects, 
what if we created openstack-api as it's own top level project. So a 
change could be targeted at OS API v3 and glance. Or OS APIv3 and nova, etc?

Maybe someone with more launchpad-fu would have better suggestions, but 
it would be really good to come up with some consistent way to track 
things we want to change for consistency.

	-Sean

-- 
Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com