groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 37/39: FOR-RELEASE: Relocate tagging item.


From: G. Branden Robinson
Subject: [groff] 37/39: FOR-RELEASE: Relocate tagging item.
Date: Tue, 31 May 2022 20:32:32 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit 6e5eb913251e1bec0004bd73cd0353bd47980b7e
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue May 31 17:47:31 2022 -0500

    FOR-RELEASE: Relocate tagging item.
    
    * Put the Git tagging item at the end of the procedure, and provide an
      example command.
    * Update Unicode data import example so people don't worry that we
      forgot about Unicode 14.
---
 FOR-RELEASE | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/FOR-RELEASE b/FOR-RELEASE
index e89e3ecc..665301fd 100644
--- a/FOR-RELEASE
+++ b/FOR-RELEASE
@@ -9,9 +9,6 @@ This file describes how to prepare 'groff' for a new release.
 
 ########################################################################
 
-* Increment the version number.  groff requires an explicit three-part
-  version, major.minor.revision, due to the .Y register.
-
 * Update font description files that we generate from external data and
   provide with our source distribution.
 
@@ -27,7 +24,7 @@ This file describes how to prepare 'groff' for a new release.
   src/utils/afmtodit/make-afmtodit-tables to update
   src/utils/afmtodit/afmtodit.tables.
 
-  [1] E.g., <https://www.unicode.org/Public/13.0.0/ucd/UnicodeData.txt>.
+  [1] E.g., <https://www.unicode.org/Public/14.0.0/ucd/UnicodeData.txt>.
       Check for the latest _released_ version of Unicode at the time.
       Data for the forthcoming release may be available.
   [2] <https://github.com/adobe-type-tools/agl-aglfn/blob/master/\
@@ -50,3 +47,9 @@ This file describes how to prepare 'groff' for a new release.
   copyright.
 
 * Update the copyright year with 'update-copyright.sh'.
+
+* 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]