openstack
/
neutron-specs
Code Issues Proposed changes

Add requirement for APIImpact flag 

Adds a requirement for an APIImpact flag in
the commit message for a proposed spec if it proposes
changes to the Neutron REST API. This will make it
much easier for people such as the API WG who want to
review API changes across OpenStack to find and
review proposed API changes.

Change-Id: I21f1b9c645bd40b8c1f2e5e627c4dd5a667431dc
This commit is contained in:
Chris Yeoh 2014-10-29 12:47:59 +10:30
parent e19c6133f1
commit 9d74fe4868
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
specs/template.rst
View File

@ -15,6 +15,15 @@ https://blueprints.launchpad.net/neutron/+spec/example
Introduction paragraph -- why are we doing anything? A single paragraph of
prose that **operators, deployers, and developers** can understand.
If your specification proposes any changes to the Neutron REST API such
as changing parameters which can be returned or accepted, or even
the semantics of what happens when a client calls into the API, then
you should add the APIImpact flag to the commit message. Specifications with
the APIImpact flag can be found with the following query::
https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs+message:apiimpact,n,z
Problem Description
===================