Update RFE documentation to clarify when the tag is not appropriate

Adds a passage to clarify that the 'rfe' tag is not to be used for work
that is already well-defined, to avoid code being submitted before proper
discussion can take place.

Change-Id: I20a1a87b263154e8b7726da08bfb615b272ba4c1

diff --git a/doc/source/policies/blueprints.rst b/doc/source/policies/blueprints.rst
index bb0e970013272b44c36b43aac35b6f0cf9922ae5..72a6a4d849b3d6b321b414a3297bf440436a1f88 100644 (file)
--- a/doc/source/policies/blueprints.rst
+++ b/doc/source/policies/blueprints.rst
@@ -45,10 +45,12 @@ is submitted.
 This allows the team to verify the validity of a feature request before the
 process of submitting a neutron-spec is undertaken, or code is written.  It
 also allows the community to express interest in a feature by subscribing to
-the bug and posting a comment in Launchpad. Note the temptation to game the
-system exists, but given the history in Neutron for this type of activity, it
-will not be tolerated and will be called out as such in public on the mailing
-list.
+the bug and posting a comment in Launchpad. The 'rfe' tag should not be used
+for work that is already well-defined and has an assignee. If you are intending
+to submit code immediately, a simple bug report will suffice. Note the
+temptation to game the system exists, but given the history in Neutron for this
+type of activity, it will not be tolerated and will be called out as such in
+public on the mailing list.
 
 RFEs can be submitted by anyone and by having the community vote on them in
 Launchpad, we can gauge interest in features. The drivers team will evaluate