<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi<br>
</p>
On 11/06/2017 02:44 PM, Andreas Neumann wrote:<br>
<blockquote type="cite"
cite="mid:cc189413f52b33d4d9f143801ea00dc4@carto.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Hi,</p>
<p><br>
</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0">Can you point me towards the issue
reports with the information from the crash dialog?<br>
<br>
<br>
</blockquote>
<p>I will try to report the crashes better. However, the crashes
are often not so easy to reproduce and not so easy to describe
what I did. But they happen quite often.</p>
</blockquote>
I understand your frustration as an early adopter, please don't get
me wrong. You report a lot and with high quality Please keep this
up.<br>
<br>
I'll have a look at those crashes, but let's keep focused here and
discuss the release strategy.<br>
<br>
I think especially with the demand for stability you raise here it's
important that we don't talk about "lifting feature freeze" but
about what can we do to ship:<br>
<br>
a) everything we want from a code-perspective<br>
b) a high quality, stable release (on which we can and will also
improve in subsequent patch releases)<br>
c) within a finite timeframe<br>
<br>
Best regards<br>
Matthias<br>
<br>
</body>
</html>