[Dune-devel] Getting rid of staging
Carsten Gräser
graeser at math.fau.de
Thu Mar 27 09:55:01 CET 2025
Dear Christoph,
regarding the specific move of dune-assembler to staging:
The aim is to place it in the same location as dune-functions
and moving dune-functions somewhere else may imply some fallout.
Am 26.03.25 um 21:47 schrieb Christoph GrĂ¼ninger:
> I don't like the staging group in our GitLab. There is no meaning,
> process, or agreement neither how projects enter it nor how projects
> leave it.
That's exactly the same for the other gitlab groups and their
naming that have been added without discussion among the core
developers, e.g. PDELab, dune-fem, fufem, spack, COPASI, dune-course, ...
We may discuss all of them, decide on a common naming convention,
and place the burden of renaming according to the convention
on all module maintainers. Or may simply live with the current
status quo, because it's not worth to spend time on this.
I strongly recomment the latter.
If you're only worried, because putting dune-assembler in staging
means that it will eventually move to core: Given the fact that we
can current give an estimated lower bound of 12 years for the
time this process takes, you can IMO relax and we may schedule
a discussion for the 2035 developer meeting.
Best
Carsten
>
> I would like to get rid of it and we need to decide where the
> projects should go (extensions or core). I want to discuss this in
> our next Dune Core meeting.
>
> This message was triggered by the recent addition of Dune Assembler.
> I do not know anything about it. My opinion is, that it should
> reside in extensions until we clarified the future of staging.
More information about the Dune-devel
mailing list