diff options
| -rw-r--r-- | README-release | 12 | ||||
| -rw-r--r-- | cfg.mk | 4 | ||||
| m--------- | gnulib | 0 |
3 files changed, 8 insertions, 8 deletions
diff --git a/README-release b/README-release index ea2199cc1..c370209fa 100644 --- a/README-release +++ b/README-release @@ -54,7 +54,8 @@ FIXME: enable excluded programs like arch? to get their manual pages? it builds and passes all tests. * While that's happening, write the release announcement that you will - soon post. + soon post. Start with the template, $HOME/announce-coreutils-X.Y + that was just created by that "make" command. Once all the builds and tests have passed, @@ -71,6 +72,7 @@ Once all the builds and tests have passed, * Announce it on Savannah first, so you can include the preferable savannah.org announcement link in the email message. + From here: https://savannah.gnu.org/projects/coreutils/ click on the "submit news", then write something like the following: @@ -86,13 +88,7 @@ Once all the builds and tests have passed, Then go here to approve it: https://savannah.gnu.org/news/approve.php?group=coreutils -* Send the gpg-signed announcement mail, e.g., - - To: info-gnu@gnu.org - Cc: coordinator@translationproject.org, coreutils@gnu.org - Cc: coreutils-announce@gnu.org - Subject: coreutils-X.Y released [stable] - Mail-Followup-To: bug-coreutils@gnu.org +* Send the announcement email message. * Approve the announcement here: http://lists.gnu.org/mailman/admindb/coreutils-announce @@ -331,6 +331,10 @@ sc_space_before_open_paren: else :; \ fi +# Override the default Cc: used in generating an announcement. +announcement_Cc_ = $(translation_project_), \ + coreutils@gnu.org, coreutils-announce@gnu.org + include $(srcdir)/dist-check.mk update-copyright-env = \ diff --git a/gnulib b/gnulib -Subproject 0c6cf5ab43555377b99d94febb2d6f23fc3d2cb +Subproject e6addf84d6331d634b5d76db03f59851f3de889 |