[Dune-devel] maintenance releases not including all core modules

[Ansgar Burchardt]

On Thu, 2018-04-05 at 10:11 +0200, Christian Engwer wrote:
> I agree with Jö, for the user it is much clearer if we keep the
> scheme
> over all modules. What would happen after the 2.5.2 release? If we
> skip dune-istl and release a maintainance release for dune-istl and
> dune-geometry afterwards, would it then be common 2.5.2, geometry
> 2.5.3 and istl 2.5.2? This sounds like a source of big confusion to
> me.

We have this already with non-core modules: a lot of modules use 2.6.X
for releases compatible with DUNE 2.5(.Y) where X might not be equal to
Y.

Instead of DUNE 2.6.X, we could only have a DUNE 2.6 release page which
points to the (current) dune-common 2.6.X, dune-istl 2.6.Y, ...
releases.

Ansgar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6519 bytes
Desc: not available
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20180405/920d5d4b/attachment.bin>