X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/2ed0e35f8662e46abf2d4b591453c82a66581d99..e476c87d935519d5069d44d1628aa3d5741dd81b:/HACKING?ds=sidebyside diff --git a/HACKING b/HACKING index 0fffc9c2..e1d59f01 100644 --- a/HACKING +++ b/HACKING @@ -4,6 +4,11 @@ This file attempts to describe the rules to use when hacking Bison. Don't put this file into the distribution. Don't mention it in the ChangeLog. +Everything related to the development of Bison is on Savannah: + + http://savannah.gnu.org/projects/bison/ + + * Administrivia ** If you incorporate a change from somebody on the net: @@ -21,9 +26,18 @@ The correct response to most actual bugs is to write a new test case which demonstrates the bug. Then fix the bug, re-run the test suite, and check everything in. + +* Hacking + ** Visible changes Which include serious bug fixes, must be mentioned in NEWS. +** Translations +Only user visible strings are to be translated: error messages, bits +of the .output file etc. This excludes impossible error messages +(comparable to assert/abort), and all the --trace output which is +meant for the maintainers only. + * Test suite @@ -38,11 +52,10 @@ release: that 1. Bison compiles cleanly, 2. the parsers it produces compile cleanly too. -- Change tests/bison to run `valgrind -q bison' to run Bison under - Valgrind. - -- Run the test suite with `./testsuite PREPARSER='valgrind -q' to make - sure the parser behave properly. +- run `make maintainer-check' which: + - runs `valgrind -q bison' to run Bison under Valgrind. + - runs the parsers under Valgrind. + - runs the test suite with G++ as C compiler... - Change tests/atlocal/CFLAGS to add your preferred options. For instance, `-traditional' to check that the parsers are K&R. Note @@ -50,8 +63,6 @@ release: but currently is actually GNU C, nor for lalr1.cc, which anyway is not exercised yet in the test suite. -- Change tests/atlocal/CC to use a C++ compiler. - * Release Procedure @@ -59,14 +70,10 @@ release: See above. ** Update the foreign files -Running `make update' in the top level should make it all for you. -This covers PO files too. Beware that it happens that some PO files -contain serious problems and are rejected by recent Gettext releases: -fix them all, and complain to the Translation Project! - -Note that there might be *new* PO files. Don't forget to update the -whole machinery, which not only includes LINGUAS, but `cvs add'ing the -PO files too. +Running `./bootstrap' in the top level should update them all for you. +This covers PO files too. Sometimes a PO file contains problems that +causes it to be rejected by recent Gettext releases; please report +these to the Translation Project. ** Update NEWS The version number, *and* the date of the release (including for @@ -96,13 +103,17 @@ In configure.ac. Run `make', check this in. ** Announce Complete/fix the announcement file, and send it at least to -info@gnu.org (if a real release, or a ``serious beta''), +info-gnu@gnu.org (if a real release, or a ``serious beta''), bison@gnu.org, and translation@iro.umontreal.ca. +Send the same announcement on the comp.compilers newsgroup. Do not +make any Cc as the moderator will throw away anything cross-posted or +Cc'ed. It really needs to be a separate message. + ----- -Copyright (C) 2002 Free Software Foundation, Inc. +Copyright (C) 2002, 2003, 2004 Free Software Foundation, Inc. This file is part of GNU Bison.