<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Hi Simon,</p>
<p>Hi Oliver,</p>
<p><br>
</p>
<p>thank you for the input. I like very much the idea of a dedicated namespace for experimental functionalities. Then, we can <span>also</span> have !93 in 2.8 :)</p>
<p><br>
</p>
<p>Cheers,</p>
<p>Santiago<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dune-devel <dune-devel-bounces@lists.dune-project.org> on behalf of Simon Praetorius <simon.praetorius@tu-dresden.de><br>
<b>Sent:</b> Tuesday, July 20, 2021 11:44:15 PM<br>
<b>To:</b> dune-devel@lists.dune-project.org<br>
<b>Subject:</b> Re: [Dune-devel] DUNE 2.8 release plan: Consider functions, typetree, and uggrid?</font>
<div> </div>
</div>
<div>
<p>Hi,<br>
</p>
<p>I also thought about the idea of having an `Experimental` namespace. If we develop some new functionality but it might not be ready for production or we are not yet sure that the interface is optimal, but there are people interested in this development,
then it could be nice to have a separate namespace for this to get the code in the master branch. In my opinion, `Impl` should be reserved for implementation details. But `Experimental` as also used in dune-functions, could be a place to add new code - that
should not be a requirement for any non-experimental other feature, but could be used in other experimental code. We then just need to make sure that old experimental features - that were unsuccessful or are simply outdated - should be removed at some point
and that some experimental feature eventually move into the non-experimental part of the library.</p>
<p>Not everything can be thoroughly tested by other developers, especially if the new feature is out of the scope of the daily work. Then it would be unfair to not merge this code, but also not a good idea to merge it right away into the public interface of
the module. So, the `Experimental` namespace could be a way in the middle.<br>
</p>
<p>Best regards,<br>
Simon<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 20.07.21 um 08:47 schrieb Oliver Sander:<br>
</div>
<blockquote type="cite" cite="mid:e4d9200f-4a5d-dab2-aedb-f68152f4926b@tu-dresden.de">
Hi Santiago, <br>
<br>
<blockquote type="cite"> * For !93, Christian proposed to merge because "it does not change existing code and adds value for the 'under construction' pdelab changes.". But I am also fine discussing it a bit further. @simon, @carsten @oliver Any opinions to
this? <br>
</blockquote>
<br>
I do not have an opinion on this. <br>
<br>
If you are not sure about the final interface then maybe a namespace <br>
like 'Impl' or 'Experimental' is a good place? <br>
<br>
Best, <br>
Oliver <br>
<br>
<blockquote type="cite"><br>
<br>
My opinion is that !92 should be in the release, while !93 is just a -nice to have- feature.
<br>
<br>
Best, <br>
Santiago <br>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<br>
*From:* Dune-devel <a class="moz-txt-link-rfc2396E" href="mailto:dune-devel-bounces@lists.dune-project.org">
<dune-devel-bounces@lists.dune-project.org></a> on behalf of Christoph Grüninger <a class="moz-txt-link-rfc2396E" href="mailto:foss@grueninger.de">
<foss@grueninger.de></a> <br>
*Sent:* Monday, July 19, 2021 8:39:02 AM <br>
*To:* <a class="moz-txt-link-abbreviated" href="mailto:dune-devel@lists.dune-project.org">
dune-devel@lists.dune-project.org</a> <br>
*Subject:* Re: [Dune-devel] DUNE 2.8 release plan: Consider functions, typetree, and uggrid?
<br>
Hi Christian, <br>
hi Santiago, <br>
<br>
what is the status regarding your MR? Can I branch or should I wait a <br>
little bit longer? <br>
<br>
Bye <br>
Christoph <br>
<br>
Am 09.07.21 um 16:44 schrieb Christian Engwer: <br>
<blockquote type="cite">Hi Christoph, <br>
<br>
Yesterday I met with Santiago and we went through a couple of changes. <br>
There are some small last things I want to check, yes you are right, <br>
there are still some MRs that should ideally be merged before 2.8. <br>
<br>
Ciao <br>
Christian <br>
<br>
Am 9. Juli 2021 16:20:33 MESZ schrieb "Christoph Grüninger" <br>
<a class="moz-txt-link-rfc2396E" href="mailto:foss@grueninger.de"><foss@grueninger.de></a>:
<br>
<br>
Hi Carsten, <br>
hi Oliver, <br>
hi Christian, <br>
<br>
Markus and I, we are preparing the Dune 2.8 release for the core <br>
modules. Should we also do dune-typetree, dune-functions, and <br>
dune-uggrid, similar as I did for Dune 2.7? <br>
<br>
I am under the impression, that you might want to merge stuff prior to <br>
the branching: <br>
typtree: <br>
!92 Add tree transformation to dynamic power nodes <br>
!93 Resolve "TreeInfo interface is not suitable for dynamic nodes" <br>
functions: <br>
!300: fix some minor issues which clang++11 complains about <br>
!278: [WIP] Provide test and fix for interpolation of general vector <br>
valued functions <br>
<br>
It's kind of sad, that we were not able to merge typetree into common. <br>
Maybe this can happen after Dune 2.8. <br>
<br>
Bye <br>
Christoph <br>
<br>
Am 24.06.21 um 11:42 schrieb Markus Blatt: <br>
<br>
Dear users and developers, <br>
<br>
<br>
we will be preparing a DUNE 2.8 release this summer. I will be <br>
the release <br>
manager and Christoph plans to help me with this task. The current <br>
tentative schedule for the release is as follows: <br>
<br>
2021-07-09 (evening): Creation of release branches. From that <br>
time on only <br>
bugfixes or very important features will be backported to the <br>
release branches. <br>
2021-07-16 (evening): Feature freeze. Only bug fixes will be <br>
backported and <br>
accepted to the release branches <br>
2021-07-19: First release candidate. This and further candidates <br>
will be <br>
announced on the DUNE mailing lists. <br>
<br>
Final release is planned for 2021-07-30, but that should be <br>
treated as a <br>
rather soft date. We will release once release candidates have <br>
been tested <br>
and we have not received any further bug reports. <br>
<br>
As always we appreciate your help with testing and backported. <br>
Please <br>
always <br>
keep in mind that saying "I tested and found no issues" is <br>
always better <br>
than <br>
not reporting back in this case. <br>
<br>
Cheers, <br>
<br>
Markus <br>
<br>
</blockquote>
<br>
-- <br>
Als wär es nix, leb' ich von [IT] und mach' nur, was ich lieb' <br>
Lebe wie im Paradies, womit hab' ich das verdient? <br>
Die Wahrheit ist: Hab' ich nicht, ich bin nur reicher beschenkt <br>
Als jemand in einem armen Land mit dem gleichen Talent <br>
[frei nach Tua von Die Orsons - Oioioiropa] <br>
<br>
_______________________________________________ <br>
Dune-devel mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:Dune-devel@lists.dune-project.org">Dune-devel@lists.dune-project.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a>
<a class="moz-txt-link-rfc2396E" href="https://lists.dune-project.org/mailman/listinfo/dune-devel">
<https://lists.dune-project.org/mailman/listinfo/dune-devel></a> <br>
<br>
_______________________________________________ <br>
Dune-devel mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:Dune-devel@lists.dune-project.org">Dune-devel@lists.dune-project.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a>
<br>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dune-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dune-devel@lists.dune-project.org">Dune-devel@lists.dune-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.dune-project.org/mailman/listinfo/dune-devel">https://lists.dune-project.org/mailman/listinfo/dune-devel</a></pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Dr. Simon Praetorius
Technische Universität Dresden
Institute of Scientific Computing
phone: +49 351 463-34432
mail: <a class="moz-txt-link-abbreviated" href="mailto:simon.praetorius@tu-dresden.de">simon.praetorius@tu-dresden.de</a>
web: <a class="moz-txt-link-freetext" href="https://tu-dresden.de/mn/math/wir/das-institut/beschaeftigte/simon-praetorius">https://tu-dresden.de/mn/math/wir/das-institut/beschaeftigte/simon-praetorius</a></pre>
</div>
</body>
</html>