Remove APIImpact flag instruction
This removes the description in the specification template that describes use of the APIImpact flag, since ironic doesn't use that flag. Change-Id: I9254f724f9a07fbf86119fc96559eed8411e3df0
This commit is contained in:
parent
3e7471c854
commit
3c21f5d64e
|
@ -8,7 +8,8 @@
|
|||
Title of the Spec
|
||||
=================
|
||||
|
||||
Include the URL of your launchpad bug with ``rfe`` tag:
|
||||
Include the URL of your launchpad bug (which should be tagged with ``rfe``
|
||||
tag):
|
||||
|
||||
https://bugs.launchpad.net/ironic/+bug/XXXXXX
|
||||
|
||||
|
@ -38,14 +39,6 @@ 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 Ironic 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/ironic-specs+message:apiimpact,n,z
|
||||
|
||||
* If you are unsure whether this proposal is aligned with the project's
|
||||
mission and scope, you are encouraged to submit a minimal spec to get
|
||||
feedback early, before investing the effort in a complete specification.
|
||||
|
|
Loading…
Reference in New Issue