[Dune-devel] Dune 2.11: Release tags created

Christoph Grüninger foss at grueninger.de
Fri Jan 23 19:50:58 CET 2026


Hi Oliver,
thanks you so much for preparing the Dune 2.11!

The tar balls are the default way to create packages for Linux 
distributions and similar systems like brew. Without official tarballs, 
I would have to create them myself with git archive and it would not 
have a signature that could be verified with our download folder.

Not sure if this is enough of an argument to have the extra work. For 
the core modules I would expect is. For openSuse I package some of the 
staging modules to. In extra I don't package.

Bye
Christoph


Am 23.01.26 um 11:40 schrieb Oliver Sander:
> Dear Dune development community,
> 
> I have just introduced v2.11.0 tags on the releases/2.11 branches of the 
> following modules:
> 
>    dune-common
>    dune-geometry
>    dune-grid
>    dune-localfunctions
>    dune-istl
> 
>    dune-assembler
>    dune-typetree
>    dune-uggrid
>    dune-functions
> 
>    dune-grid-glue
>    dune-foamgrid
>    dune-vtk
>    dune-curvedgeometry
>    dune-curvedgrid
>    dune-gmsh4
> 
> Tarballs have been created and signed, but my schedule doesn't allow me 
> to do the uploading and necessary website redactions right now. I'll do 
> that in one of the following days. Apologies.
> 
> I do wonder whether we still need those tarballs in a world where git is 
> so pervasive.
> 
> Best,
> Oliver
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at lists.dune-project.org
> https://lists.dune-project.org/mailman/listinfo/dune-devel

-- 
Most customers will not accept source code with compile errors in it.
                  Dan Saks, CppCon 2016 (https://youtu.be/D7Sd8A6_fYU)




More information about the Dune-devel mailing list