maint: maintainer-release-check.

[bison.git] / README-hacking

diff --git a/README-hacking b/README-hacking
index e481da75022dafcad5f79eca5bc7bea7e5b87c4a..97c73a80c5b3e506841b6d9849eb717bfe70b504 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -15,10 +15,10 @@ First, if it is a large change, you must make sure they have signed
 the appropriate paperwork.  Second, be sure to add their name and
 email address to THANKS.
 
-** If a change fixes a test, mention the test in the log entry.
+** If a change fixes a test, mention the test in the commit message.
 
 ** Bug reports
-If somebody reports a new bug, mention his name in the log entry
+If somebody reports a new bug, mention his name in the commit message
 and in the test case you write.  Put him into THANKS.
 
 The correct response to most actual bugs is to write a new test case
@@ -180,6 +180,9 @@ release:
 - Build with -DGNULIB_POSIXCHECK.  It suggests gnulib modules that can
   fix portability issues.
 
+- Check with `make syntax-check' if there are issues diagnosed by
+  gnulib.
+
 - run `make maintainer-check' which:
   - runs `valgrind -q bison' to run Bison under Valgrind.
   - runs the parsers under Valgrind.
@@ -197,6 +200,9 @@ release:
   Bison's included XSLT style sheets with the output of --report=all and
   --graph.
 
+- running `make maintainer-release-check' takes care of running
+  maintainer-check, maintainer-push-check and maintainer-xml-check.
+
 - Change tests/atlocal/CFLAGS to add your preferred options.  For
   instance, `-traditional' to check that the parsers are K&R.  Note
   that it does not make sense for glr.c, which should be ANSI,
@@ -241,7 +247,7 @@ occurrences of PACKAGE_COPYRIGHT_YEAR in configure.ac.
 The version number, *and* the date of the release (including for
 betas).
 
-** Mention the release name in a commit log
+** Mention the release name in a commit message
 Should have an entry similar to `Version 2.3b.'.
 
 ** Tag the release
@@ -251,7 +257,7 @@ similar to:
 
   git tag -a v2.3b
 
-The log message can be simply:
+The commit message can be simply:
 
   Bison 2.3b