Add another patch scoping bullet point to effective_neutron

This patch adds an alternative wording of the patch sizing/scoping
recommendation that was left out of [1]

[1] https://review.openstack.org/#/c/230217

Change-Id: I64b4f4aca90c19d7dbc81a8126a7254d64876699

diff --git a/doc/source/devref/effective_neutron.rst b/doc/source/devref/effective_neutron.rst
index f62d2cff6cfbb5788578f8c462515586341418fc..9d3df6d72cda623aac7dcebb075ee6860a7e4f13 100644 (file)
--- a/doc/source/devref/effective_neutron.rst
+++ b/doc/source/devref/effective_neutron.rst
@@ -194,6 +194,11 @@ Scoping your patch appropriately
   in the refactor and changes required for the fix/feature. If it's a bug fix,
   try to implement the fix before the refactor to avoid making cherry-picks to
   stable branches difficult.
+* Consider your reviewers' time before submitting your patch. A patch that
+  requires many hours or days to review will sit in the "todo" list until
+  someone has many hours or days free (which may never happen.) If you can
+  deliver your patch in small but incrementally understandable and testable
+  pieces you will be more likely to attract reviewers.
 
 Nits and pedantic comments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~