X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/95611b56170082a1152416368f519f4392123fdd..e35bc778cb1c45845d7d8d3b659f555773d2828d:/HACKING?ds=sidebyside diff --git a/HACKING b/HACKING index f16d4f60..ec3d36d3 100644 --- a/HACKING +++ b/HACKING @@ -203,8 +203,11 @@ release: * Release Procedure -** Try to get the *.pot files to the Translation Project at least one week -before a stable release, to give them time to translate them. +** Try to get the *.pot files to the Translation Project at least one +week before a stable release, to give them time to translate them. +Before generating the *.pot files, make sure that po/POTFILES.in and +runtime-po/POTFILES.in list all files with translatable strings. +This helps: grep -l '\<_(' * ** Tests See above. @@ -340,19 +343,21 @@ To generate a template announcement file: make RELEASE_TYPE=alpha gpg_key_ID=F125BDF3 announcement -where alpha can be replaced by beta or major and F125BDF3 should be replaced -with your key ID. For an example of how to fill out the template, search the -mailing list archives for the most recent release announcement. +where alpha can be replaced by beta or stable and F125BDF3 should be +replaced with your key ID. -Complete/fix the announcement file, and send it at least to -info-gnu@gnu.org (if a real release, or a ``serious beta''), -bug-bison@gnu.org, help-bison@gnu.org, bison-patches@gnu.org, -and coordinator@translationproject.org. +Complete/fix the announcement file. The generated list of recipients +(info-gnu@gnu.org, bug-bison@gnu.org, help-bison@gnu.org, +bison-patches@gnu.org, and coordinator@translationproject.org) is +appropriate for a stable release or a ``serious beta''. For any other +release, drop at least info-gnu@gnu.org. For an example of how to fill +out the rest of the template, search the mailing list archives for the +most recent release announcement. -Send the same announcement on the comp.compilers newsgroup by sending -email to compilers@iecc.com. 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. +For a stable release, send the same announcement on the comp.compilers +newsgroup by sending email to compilers@iecc.com. 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. ** Bump the version number In configure.ac. Run `make'. So that developers don't accidentally add new @@ -365,7 +370,8 @@ Push these changes. ----- -Copyright (C) 2002-2005, 2007-2010 Free Software Foundation, Inc. +Copyright (C) 2002, 2003, 2004, 2005, 2007, 2008, 2009, 2010 Free +Software Foundation, Inc. This file is part of GNU Bison.