[Dune-devel] maintenance releases not including all core modules
Jö Fahlke
jorrit at jorrit.de
Wed Apr 4 17:52:10 CEST 2018
Am Mi, 4. Apr 2018, 17:32:08 +0200 schrieb Ansgar Burchardt:
> when preparing the DUNE 2.5.2rc1 release (to have a final release of
> DUNE 2.5 with the changes that are pending in the release branch), I
> noticed that not all modules have changes. So I only prepared updates
> for the one that do, however the page template for releases expects all
> modules to be updated.
>
> For now I've created symlinks (e.g. dune-geometry-2.5.2rc1.tar.gz is a
> symlink pointing to dune-geometry-2.5.1.tar.gz) so that the download
> links work. It might be a bit confusing that extracting the archive
> will give dune-geometry-2.5.1 though even though the archive name
> suggests it to contain 2.5.2rc1 (which does not exist).
>
> I wonder if we should either (a) extend the page template to include
> modules with different (older) versions or (b) always release all
> modules in sync even when there are no changes. I myself would prefer
> (a).
Actually, for a release I'd go with (b), at least for the core modules. Since
we otherwise try to stay in sync, this has way less potential for confusion.
Regards,
Jö.
--
Jorrit (Jö) Fahlke, Institute for Computational und Applied Mathematics,
University of Münster, Orleans-Ring 10, D-48149 Münster
Tel: +49 251 83 35146 Fax: +49 251 83 32729
A mathematician is a device to turn coffee into theorems.
-- Paul Erdős
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20180404/30854441/attachment.sig>
More information about the Dune-devel
mailing list