Added instructions in CONTRIBUTING to remind developers to write unit tests for bugfi...

diff --git a/docs/CONTRIBUTING b/docs/CONTRIBUTING
index f5d7ebc..9032b42 100644 (file)
--- a/docs/CONTRIBUTING
+++ b/docs/CONTRIBUTING
@@ -66,6 +66,7 @@ This is a relatively easy, solid and transparent way to handle all requests in o
   we know for bigger changes this is not always feasible.  Just try to keep the merges about bigger "clean changesets".
 * Your code should not introduce any compile warnings or errors.  And also,
   no regressions but that's harder to check.
+* Unit tests should be written to verify bug fixes and new functionality.
 That said, you can always ask us to check on your stuff or ask for advice.