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 Designate 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: I4ce6a27127cd0af21d4a160ce446076c38258874
This commit is contained in:
parent
eeaadac19f
commit
bef5ed102a
|
@ -22,6 +22,15 @@ https://blueprints.launchpad.net/designate/+spec/example
|
|||
|
||||
Introduction paragraph -- why are we doing anything?
|
||||
|
||||
If your specification proposes any changes to the Designate 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/designate-specs+message:apiimpact,n,z
|
||||
|
||||
|
||||
Problem description
|
||||
===================
|
||||
|
||||
|
|
Loading…
Reference in New Issue