openstack/glance-specs
Code Issues Proposed changes

Add requirement for APIImpact flag

Browse Source 
Adds a requirement for an APIImpact flag in
the commit message for a proposed spec if it proposes
changes to the Glance 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: Ic83a797b3feae28052abba78ac9abc4a07f4063e
This commit is contained in:
Chris Yeoh 2014-10-29 12:38:19 +10:30
parent 35dc41cf23
commit d3e34471f1
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
specs/template.rst
View File

@ -40,6 +40,14 @@ Some notes about using this template:
having to look at additional files which can not be viewed in gerrit. It
will also allow inline feedback on the diagram itself.
* If your specification proposes any changes to the Glance 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/glance-specs+message:apiimpact,n,z
Problem description
===================