From dc38a8531cc400bc163595357cedbfaea9e1047f Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Thu, 19 Jun 2025 14:34:34 -0700 Subject: [PATCH] doc: more release stuff in HACKING. * HACKING: more on announcement and signature. Still incomplete. --- HACKING | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/HACKING b/HACKING index 0f5263f2f..f060e0ded 100644 --- a/HACKING +++ b/HACKING @@ -610,6 +610,7 @@ --news=NEWS \ --url-directory=https://$host.gnu.org/gnu/$pkg and merge this with the just-written announcement file. + Make sure the final text does not include "no matching" lines. * Run "make git-upload-release". For pretest releases: "DEVEL_SNAPSHOT=1 make git-upload-release". @@ -621,9 +622,11 @@ meantime), and invoke the 'gnupload' script sign and upload them to the correct locations. - If you need to sign with a non-default key, you can use "make - GNUPLOADFLAGS='--user KEY' git-upload-release". There can be a delay - of up to several minutes before the new files appear on the server. + There can be a delay of up to several minutes before the new files + appear on the server. + + If you need to sign with a non-default key, you can use: + "make GNUPLOADFLAGS='--user KEY' git-upload-release" * Push the new release tag: git push origin master tag v$(VERSION). You can view unpushed local-only tags with git push --tags --dry-run @@ -660,12 +663,15 @@ is a stable one, the announcement also goes to ; if it is an alpha or beta release, announcement should be sent also to , to maximize the possibility of early - testing on the widest variety of systems. Finally, copy an abridged - version of the announcement into the NEWS feed at: - . - Be sure to link a version to the complete announcement (from - the version you sent to the automake list, as archived at - ). + testing on the widest variety of systems. + + Finally, copy an abridged version of the announcement into the NEWS + feed at: . Be sure to + link a version to the complete announcement (as archived at any of the + lists, e.g., + ). It's useful + to do this for all kinds of releases, again to help pretests be seen + and actually tested by as many people as possible. --------- Copyright (C) 2003-2025 Free Software Foundation, Inc. -- 2.47.3