<pre>>I share your concern but no one has actually the time or manpower to <br>> solve these bugs, and to be honest I don't think that postponing the <br>> release any longer will improve the situation. This release has enough <br>
> good points to compensate, I hope all this shiny stuff will blind the <br>> users enough so they don't see the little problems.<br>><br>> If corporate users want a bug-free release, they'll have to invest in <br>
> maintaining it. Some institutes I know are already lurking on this list <br>> and I hope they will be able to push this kind of effort trough their <br>> hierarchy, I'll also looking forward a big announcement in the coming <br>
> week.<br>><br>> So +1 for release<br></pre><br>Perhaps the problem is uderstand what mean "release version".<br>If it is only a snapshot of all available to a timestamp date,<br>or if it mean a version that is more stable than the trunk version.<br>
<br>However <br>I would suggest to consider the choice of update the geos to the 3.3.0 version (released some day ago) before to release the qgis 1.7<br>To have almost the more recent and stable version of it.<br><br>regards,<br clear="all">
<br>-- <br>-----------------<br>Andrea Peri<br>. . . . . . . . . <br>qwerty אטלעש<br>-----------------<br><br>