gbranden pushed a commit to branch master
in repository groff.

commit df0367f42ad4d52c90c231ca78de4e0a6b93b98f
Author: G. Branden Robinson <[email protected]>
AuthorDate: Fri Apr 3 02:17:16 2026 -0500

    FOR-RELEASE: Clarify and update procedures.
---
 FOR-RELEASE | 36 +++++++++++++++++++++++-------------
 1 file changed, 23 insertions(+), 13 deletions(-)

diff --git a/FOR-RELEASE b/FOR-RELEASE
index 177089d34..6e43668b5 100644
--- a/FOR-RELEASE
+++ b/FOR-RELEASE
@@ -56,16 +56,25 @@ Before Release
 * Update the "gnulib" sub-module and "bootstrap" script to the latest
   stable versions.  See the "HACKING" file for instructions.
 
+Subsequent steps tend to be repeated as multiple release candidates are
+prepared, as applicable.
+
+*** Begin loop
+
+* Announce a code freeze to the groff development mailing list.  The
+  maintainer must decide upon the scope, duration, and "hardness" of the
+  freeze.
+
 * Update the release version number where it is hard-coded or
   represented as "next".
   + NEWS (append or remove "release candidate" as applicable)
   + arch/mingw/grap2graph.cmd
 
 * Update in "src/roff/groff/groff.cpp" the 'printf' that displays the
-  copyright to include the current year if it is not present.  (If no
-  copyrightable changes to the project's code have been made in the
-  current calendar year, use the most recent year in which they have;
-  see the "HACKING" file.)
+  copyright notice to include the current year if it is not present.
+  (If no copyrightable changes to the project's code have been made in
+  the current calendar year, use the most recent year in which they
+  have; see the "HACKING" file.)
 
 * Run the "set-man-page-time-stamps" Makefile target from your build
   directory to fix up the stamps on the man pages.
@@ -109,6 +118,7 @@ Before Release
 
   https://www.gnu.org/prep/maintain/maintain.html#Automated-Upload-Procedure
 
+*** End loop
 
 After Release
 =============
@@ -117,14 +127,8 @@ After Release
   and its detached signature file to percolate through GNU's mirror
   network.
 
-* For official releases, update the groff home page.
-
-* Make an email announcement per the "ANNOUNCE" (release notes) file.
-
-* If warranted, update the "ANNOUNCE" file to make it a template for the
-  next release.
-
-* Update the groff home page, which is kept under CVS revision control.
+* For official releases, update the groff home page, which is kept under
+* CVS revision control.
 
   $ cvs -z3 -d:ext:[email protected]:/web/groff co groff
 
@@ -187,7 +191,13 @@ After Release
   reason the site's web server doesn't seem to always update the
   metadata that assist the browser to recognize a stale cache entry.
 
-* Update groff's entry at the FSF's Free Software Directory.
+* Make an email announcement per the "ANNOUNCE" (release notes) file.
+
+* If warranted, update the "ANNOUNCE" file to make it a template for the
+  next release.
+
+* For official releases, update groff's entry at the FSF's Free Software
+  Directory.
 
   https://directory.fsf.org/wiki/Groff
 

_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit

Reply via email to