gbranden pushed a commit to branch master
in repository groff.
commit 2d86fe0306e2ab4e3b09ef952927164582a5f20d
Author: G. Branden Robinson <[email protected]>
AuthorDate: Mon Jan 26 16:08:50 2026 -0600
FOR-RELEASE: Revise sequencing and add details.
* Drop "BUG-REPORT" from list of places the version number is
hard-coded.
* Qualify when "NEWS" and "doc/webpage.ms" should be updated with a new
version number (always, and only for final release, respectively).
* Add instructions for signing tags and pushing them.
* Add step for making an announcement.
* Make clear that "make distcheck" should be done immediately before
_and_ after generation of a Git tag. The former to be sure the source
tree is in a sound state, and the latter to produce a distribution
archive that unpacks to a directory name that matches the tag, and,
when the version number increments, so that the build installs certain
files to a directory with the correct name, such as
"/usr/share/groff/1.24.0" rather than "/usr/share/groff/1.23.0"
---
FOR-RELEASE | 33 +++++++++++++++++++++------------
1 file changed, 21 insertions(+), 12 deletions(-)
diff --git a/FOR-RELEASE b/FOR-RELEASE
index 96d48bd4f..9cbf59841 100644
--- a/FOR-RELEASE
+++ b/FOR-RELEASE
@@ -46,10 +46,9 @@ This file describes how to prepare 'groff' for a new release.
* Update the release version number where it is hard-coded or
represented as "next".
- + NEWS
- + BUG-REPORT
+ + NEWS (append "release candidate" as applicable)
+ arch/mingw/grap2graph.cmd
- + doc/webpage.ms
+ + doc/webpage.ms (only for final release)
* If the major or minor version number is being incremented, split off
a historical ChangeLog file and add it to `EXTRA_DIST` in Makefile.am.
@@ -60,21 +59,31 @@ This file describes how to prepare 'groff' for a new
release.
current calendar year, use the most recent year in which they have;
see the 'HACKING' file.)
-* Increment the version number by tagging the release, beta, or release
- candidate. groff requires an explicit three-part version,
- major.minor.revision, due to the .Y register.
-
- $ git tag 1.23.0.rc1
-
* Run the "set-man-page-time-stamps" Makefile target from your build
directory to fix up the stamps on the man pages.
* Build (and test!) a distribution archive with "make distcheck". It's
- important to do this especially after tagging a first release
+ not a good idea for any tests to be failing, but if they are, note the
+ fact prominently in the release notes.
+
+* Increment the version number by tagging the release, beta, or release
+ candidate. Sign the tag. groff requires an explicit three-part
+ version, major.minor.revision, due to the .Y register. Push this
+ signed tag to the repository.
+
+ $ git tag -s -m 'release candidate 1.24.0.rc2' 1.24.0.rc2
+ $ git push origin tag 1.24.0.rc2
+
+* Build and test a distribution archive again with "make distcheck".
+ It's important to do this especially after tagging a first release
candidate, because this increments the version number visible in
installed file names (such as "/usr/share/groff/1.24.0") and in the
archive file, so that it unpacks to an appropriately named source
directory.
-* groff 1.24.0: Edit the groff home page. Revise the sentence "Most
- commands installed by groff recognize this option." to say "All".
+* For final releases, update the groff home page.
+
+* Make an announcement per the "ANNOUNCE" file.
+
+* groff 1.24.0: Revise the sentence "Most commands installed by groff
+ recognize this option." to say "All".
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
