X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=HACKING;h=fdadada41a1576cab7569a24ff70df6888dcc8a5;hb=0ac06406dcc6cf9c5f1fbeef340764e73cc8eae0;hp=fac35be149c1f372f6691205fad7dbd33b0fcb95;hpb=60bfe0b9af62baae3498fe8688703570ecb1a93e;p=platform%2Fupstream%2Fautomake.git

diff --git a/HACKING b/HACKING
index fac35be..fdadada 100644
--- a/HACKING
+++ b/HACKING
@@ -121,7 +121,10 @@
 
 * Micro releases should be just bug-fixing releases; no new features
   should be added, and ideally, only trivial bugs, recent regressions,
-  or documentation issues should be addressed by them.
+  or documentation issues should be addressed by them.  On the other
+  hand, it's OK to include testsuite work and even testsuite refactoring
+  in a micro version, since a regression there is not going to annoy or
+  inconvenience Automake users, but only the Automake developers.
 
 * Minor releases can introduce new "safe" features, do non-trivial but
   mostly safe code clean-ups, and even add new runtime warnings (rigorously