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

[Steffen Müthing]

> Am 05.04.2018 um 11:53 schrieb Christian Engwer <christian.engwer at uni-muenster.de>:
> 
> On Thu, Apr 05, 2018 at 11:09:29AM +0200, Ansgar Burchardt wrote:
>> 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.
> 
> That is one of the reasons why they are not core modules. Up to now I
> always thought that it is consesus that we release core module in
> sync.

That’s also how I understand the process to work. It just makes it a lot easier not to have to
figure out which core module is at which point release, also for stuff like downloading the
tarballs.

Non-core modules are a different thing, they don’t even have to follow our coordinated release
numbers and could just go for a completely different numbering scheme, like e.g. dumux.

Steffen

> 
> Christian
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at lists.dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel
>