Andreas Enge writes: > This is already part of the ruby-team branch, which I am cc-ing along > with people who have worked on this branch. I think this is a good example of point 2 for managing branches on [1]: Any changes that can be made on the master branch, should be made on the master branch. If a commit can be split to apply part of the changes on master, this is good to do. 1: https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html Looking at the number of packages affected from QA, this change can go straight to master, so shouldn't go via a branch.