On Mon, 20 Oct 2014 14:44:15 -0500 Anne Gentle <a...@openstack.org> wrote: > > > > > I think adding APIImpact will be useful. > > I also want to point to the addition of Compute v2 (haven't yet > proposed a spec for v2.1) to the nova-specs repo here: > > https://review.openstack.org/#/c/129329/ > > The goal is to move information from the compute-api repo into the > -specs repo. I sent an email to the PTLs in August and then added it > in the What's Up Doc Oct 7th so hopefully this doesn't take anyone by > surprise. You'll notice if you review that I don't have the template > test in place that exist for the other blueprint templates, rather > the ideal is that a new file would be added into api/v2.1 if a > blueprint affects the API design that describes the correct > response/request, error codes, and other relevant info. Also if the > feature affects faults, limits, links, pagination, and so on, the > spec review would address that in the api spec.
I think this would be a good thing to do. I've added some comments on the review. Also here is the review for adding a requirement for an APIImpact flag in the commit message: https://review.openstack.org/#/c/129757/ Regards, Chris > > > > Regards, > > > > Chris > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStackfirstname.lastname@example.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev