From: Stefano Lattarini Date: Wed, 22 May 2013 18:13:41 +0000 (+0200) Subject: HACKING: it's OK to do testsuite refactoring in a micro version X-Git-Tag: v1.13.2b~41 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d9a3a4477bdc346f515786cf70568db25a167422;p=platform%2Fupstream%2Fautomake.git HACKING: it's OK to do testsuite refactoring in a micro version Reported-by: Peter Rosin Signed-off-by: Stefano Lattarini --- diff --git a/HACKING b/HACKING index 3ce2e66..194a775 100644 --- a/HACKING +++ b/HACKING @@ -111,7 +111,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