openstack/trove-specs
Code Issues Proposed changes

Merge "Add requirement for APIImpact flag"

Browse Source
This commit is contained in:
Jenkins 2014-11-17 18:17:07 +00:00 committed by Gerrit Code Review
commit a74243e079
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

@ -42,6 +42,15 @@ propose to solve this problem?
If this is one part of a larger effort make it clear where this piece ends. In
other words, what's the scope of this effort?
If your specification proposes any changes to the Trove 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/trove-specs+message:apiimpact,n,z
Configuration
-------------