gbranden pushed a commit to branch branden-2023-07-05 in repository groff. commit e0fd10babbce81a331afa1ded054343591a70334 Author: G. Branden Robinson <g.branden.robin...@gmail.com> AuthorDate: Fri Mar 31 07:29:09 2023 -0500
README.branch: Describe purpose of branch. --- README.branch | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/README.branch b/README.branch new file mode 100644 index 000000000..cc00e06d7 --- /dev/null +++ b/README.branch @@ -0,0 +1,33 @@ +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.rc5 +(or final release). + +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. + +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 following 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 the master branch is at the bottom. + +(As of this writing, level 1 changes continue to be committed directly +to the master branch.) + +The commit creating this file should of course not be merged. + +--GBR _______________________________________________ Groff-commit mailing list Groff-commit@gnu.org https://lists.gnu.org/mailman/listinfo/groff-commit