<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote type="cite"
cite="mid:CAFMUeB9FOQSd-1tYzmSnJ0ftprBXbn7eSKA_+ss=Xfj9Sbufqg@mail.gmail.com">
<div dir="auto">
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
>> Are there plans to release version 3.0.6 later
this year?<br>
> No. There will probably no 3.0.x anymore. (and even
if, it would have mostly<br>
> minor RTL fixes, no sensitive compiler fixes).<br>
It would be nice have at least one maintenance release per
year.<br>
Also some Database related bugs can be merged if there
will be 3.0.6<br>
(of course I understand, that compiler related features,
asked by<br>
African Dog will not be merged)<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Release engineering takes half a year.</div>
</div>
</blockquote>
1/2 year, so long? Also in case of fixies/point release ?<br>
(my intuitive understanding was that it is question of automated
building process, when fixies branch is taken and binaries are
compiled/build)<br>
<br>
<blockquote type="cite"
cite="mid:CAFMUeB9FOQSd-1tYzmSnJ0ftprBXbn7eSKA_+ss=Xfj9Sbufqg@mail.gmail.com">
<div dir="auto">
<div dir="auto"> We prefer to use that time to squash more bugs
and improve the compiler and libraries. <br>
</div>
</div>
</blockquote>
Yes of course. On other side improvement is neverending process, so
in some point in time "decision" must be taken.<br>
Probably this decision is based on some features, which must be
completed before releasing of new version can start ...<br>
<br>
-Laco.<br>
<br>
</body>
</html>