#2692: Inclusion of FUKA importer thorns
Reporter: tootle Status: new Milestone: ET_2023_05 Version: ET_2023_05 Type: proposal Priority: major Component: EinsteinToolkit thorn
Comment (by Roland Haas):
1. yes, please 2. only the `[submodule "fuka"]` block (which is non-functional anyway) 3. you won’t need a `ET_YYYY_MM` etc. branch in `fuka` as long as the submodule import in `KadathThorn` is a “regular” one that specifies a specific commit (that one then needs to manually update when one wants to use a newer `fuka` version) and is not auto-set to track a (changing) branch (your’s does currently have a fixed commit). If things are changed at `KadathThorn` is set to track a specific branch of `fuka` (via the `git submodule set-branch` and `git update --remote` commands) then a `ET_YYYY_MM` branch and tags of type `ET_YYYY_MM_vN` (where N starts from 0 and increases by 1 for each point [bugfix] release) are needed. These are created shortly before the release when all code is frozen (I think about 1 week before the release). See [https://docs.einsteintoolkit.org/et-docs/Release%5C_Process#Timeline%5C_for%...) and the “Release preparation II” item.
-- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2692/inclusion-of-fuka-...