[Top][All Lists]

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

[groff] 48/48: README.branch: Describe purpose of branch.

From: G. Branden Robinson
Subject: [groff] 48/48: README.branch: Describe purpose of branch.
Date: Fri, 31 Mar 2023 08:33:14 -0400 (EDT)

gbranden pushed a commit to branch branden-2023-03-31
in repository groff.

commit 5bd671f7f788f6e4f7de7fb50ee4f7953df8630d
Author: G. Branden Robinson <>
AuthorDate: Fri Mar 31 07:29:09 2023 -0500

    README.branch: Describe purpose of branch.
 README.branch | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/README.branch b/README.branch
new file mode 100644
index 000000000..e539fa251
--- /dev/null
+++ b/README.branch
@@ -0,0 +1,29 @@
+This branch is a staging ground for commits intended for cherry-picking
+to the master branch in preparation for the tagging of groff 1.23.0.rc4.
+The commits are not in chronological order of development, but in a
+subjective ordering of risk to release stability, with the earlier
+commits being less risky and the more recent ones more so.  The idea
+is to make it easy to merge many of them, or to simply choose a point
+within the series for merge and tagging as rc4.
+I'm happy to perform merge or cherry-pick operations as directed by
+Bertrand, who as maintainer may then perform the tag operation and
+distribution archive generation.
+Here are the risk categories as I conceive them.  As you read down a
+plain "git log" command from this branch, you will see the commits
+appear in the foregoing order.
+Level 6: Changes to installed, compiled code.
+Level 5: Changes to installed macro packages.
+Level 4: Changes to installed scripts.
+Level 3: Changes to build scripts.
+Level 2: Changes to test scripts.
+Level 1: Changes to documentation.
+The branch point from master is at the bottom.
+The commit creating this file should of course not be merged.

reply via email to

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