Comment (by Roland Haas):

The only docs that exist are: https://docs.einsteintoolkit.org/et-docs/Release_Process#create_branches

The script shown there should work for the Kadath codes in this ticket due to (3). They are basically the same as Kranc and its Examples repo (also a submodule with fixed git hash).

You will have to (at this point) manually handle proposal_ET_2023_05 in canuda/scalar since that is not the “default” branch and script fragment on the wiki assumes that one branches of release branches from the current head of the default branch. This most likely can (and should) be changed so that one can run the script fragment in the repository structure created by GetComponents on the master thornlist from the manifest repo and make it assume that the branching happens off the currently checked out branch (which for canuda/scalar is currently proposal_ET_2023_05). This (probably) just means removing the:

default_branch=$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')

and

git checkout $default_branch

lines. It will also affect how one learns which changes to announce (which also looks at the default branch), but that process requires some human interaction anyway.

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-importer-thorns