From 9e42ecceff823a9f966b798bda5b33463d199277 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Mon, 3 May 2010 22:00:30 +0200 Subject: doc: factor hard-coded project-specific bits from README-release, ... using the new --mail-headers option to gnulib's announce-gen, and the updated maint.mk rules to connect the pieces. * README-release: Remove hard-coded To:, Cc: etc. parts, now that they're emitted automatically into the announcement template. * cfg.mk (announcement_Cc_): Override the default. * gnulib: Update to latest, to get newer announce-gen and maint.mk. --- README-release | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) (limited to 'README-release') 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 -- cgit v1.2.3-70-g09d2