<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div></div>
<div>Hi Markus. </div>
<div>Thanks for testing. </div>
<div><br>
</div>
<div>We will make a release branch quite soon. At the moment the master works with both the master and release of dune core and we wanted to see if there was any feedback or reports on problem with the new model before tagging or branching for a release. </div>
<div><br>
</div>
<div>We are still discussing the tar vall issue. </div>
<div><br>
</div>
<div>Best </div>
<div>Andreas </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:10px; color:#575757">Sent from Samsung Mobile</div>
</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Markus Blatt <br>
Date:31/07/2014 10:50 (GMT+00:00) <br>
To: dune-devel@dune-project.org <br>
Subject: Re: [Dune-devel] ALUGrid <br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
I did forget this the last time:<br>
<br>
Congratulions to the release and thanks for all the continued effort<br>
you guys put into ALUGrid.<br>
<br>
I am currently testing the new versions and there are quite a few<br>
questions popping up during this. I will just ask them here whenever<br>
they popup.<br>
<br>
You are saying on the website: "There won't be any tar balls."<br>
While this is of course your own choice, it is rather unusual and<br>
might hinder general acceptance. E.g. there are distributions, like<br>
Debian, that always base their packages on the official release<br>
tarballs. Not having them might pose a problem. Maybe Ansgar can<br>
enlighten us about this.<br>
<br>
Anyway, not having tarballs und using autotools demands users to<br>
install the full autotools toolchain which might be a problem for some<br>
people. <br>
<br>
Your development model seems to be to have a stable master branch and<br>
develop in other branches. What I am missing is a way to checkout the<br>
release as there is no release branch (not really needed) and you do<br>
not use tags to identify the release. The latter seems mandatory to me<br>
(even more if there are no tarballs available).<br>
<br>
Could you please use "git tag [-s] v2.3" to mark your release. That way<br>
users will be able to checkout this release even in the future. If you<br>
did this, then the tags might need to get pushed "git push origin<br>
v2.3".<br>
<br>
Thanks a lot!<br>
<br>
Cheers,<br>
<br>
Markus<br>
<br>
-- <br>
Do you need more support with DUNE or HPC in general? <br>
<br>
Dr. Markus Blatt - HPC-Simulation-Software & Services <a href="http://www.dr-blatt.de">
http://www.dr-blatt.de</a><br>
Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany<br>
Tel.: +49 (0) 160 97590858<br>
</div>
</span></font>
</body>
</html>