diff options
| author | Stefano Lattarini <stefano.lattarini@gmail.com> | 2013-05-23 20:12:17 +0200 |
|---|---|---|
| committer | Stefano Lattarini <stefano.lattarini@gmail.com> | 2013-05-23 20:12:17 +0200 |
| commit | 86e45fe19374b87b6a9adaeb3ecc93e51c7d54a7 (patch) | |
| tree | e692ec2434926772c17accc76e7581f972b8e976 /HACKING | |
| parent | 8d7108702485dca61841a642202b892f8038e15c (diff) | |
| parent | 3ce4015f1bfff6277840502b080cfd2b22e05870 (diff) | |
| download | automake-86e45fe19374b87b6a9adaeb3ecc93e51c7d54a7.tar.gz | |
Merge branch 'micro' into maint
* micro:
tests: avoid '$MAKE' redirections, use 'run_make' instead
tests: avoid use of redirected 'run_make' invocations
lint: warn against redirected 'run_make' invocations
comments: next GNU make release 4.0, not 3.83
tests: fix a potential spurious failure due to global config.site
HACKING: it's OK to do testsuite refactoring in a micro version
Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -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 |