should have the major version number unchanged, the minor version number
bumped, and the micro version number reset to zero. Finally, a new
micro version should have the major and minor version numbers unchanged,
- and the micro version number bumped.
+ and the micro version number bumped by one.
For example, the first minor version after 1.13.2 will be 1.14; the
first bug-fixing version after 1.14 that will be 1.14.1; the first
* 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