<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Thank you for the follow-up, Raphael.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I’m now up to date and all works for me.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>My original message was just before the mad scramble to re-release 3.10.x with 3.0.3 and 6.3.0 (and in fact may together with the associated bug reports have prompted it). <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>My appreciation to the developers for the quick followup (doubtless displacing whatever Nyall et al meant to be doing last week….), and for doing their best to maintain a complex and very capable geospatial software ecosystem. Not easy, in the open-source or commercial software environments.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I think there are lessons to be learnt about what should trigger (and, on the flip side, be allowed in) _._._-x, _._.x, and _.x releases. In particular, given the criticality I suspect it would have been better to withdraw 3.10.2 and issue the fix as 3.10.3. And (earlier) to not try to backport the Proj4->Proj6 shift into QGIS 3.4.x at all. (And maybe to not change custom projection functionality as much between 3.10.1 and 3.10.2, waiting until 3.12.) But I realize we were scrambling to fix the darn thing rather than splitting hairs on versioning, and I think we can wait for the devs’ PTSD symptoms to abate somewhat before conclusive postmortems!<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Thanks again,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Martin<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Raphael Das Gupta <raphael.das.gupta@hsr.ch> <br><b>Sent:</b> January 28, 2020 07:16<br><b>To:</b> qgis-developer@lists.osgeo.org<br><b>Cc:</b> pergler@gmail.com<br><b>Subject:</b> Not all QGIS 3.10.2 downloads did contain the upgraded GDAL and PROJ versions (Re: [QGIS-Developer] What GDAL and PROJ versions with 3.10.2?)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Hi again<o:p></o:p></p><div><p class=MsoNormal>On 20.01.20 11:45, <a href="mailto:pergler@gmail.com">pergler@gmail.com</a> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I installed 3.10.2 (OSGeo4W installer) over the weekend, and I’m running into a bunch of issues (zoom crashes - <a href="https://github.com/qgis/QGIS/issues/33902">https://github.com/qgis/QGIS/issues/33902</a>; corrupted output from georeferencer, custom CRS that has lost its USER:xxxxx label). Before I try to pick them off one by one, is it possible the right dependencies didn’t make it into the install?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>My About… screen says I have GDAL 3.0.2 and PROJ “6.2.1 dated Nov 1”, which makes me suspicious.<o:p></o:p></p></blockquote><p>Apparently, the first Windows builds of release 3.10.2 still included older versions of GDAL/OGR and PROJ. See <a href="https://lists.osgeo.org/pipermail/qgis-developer/2020-January/thread.html#59948">this thread</a> on this list. <a href="https://lists.osgeo.org/pipermail/qgis-developer/2020-January/060001.html">https://lists.osgeo.org/pipermail/qgis-developer/2020-January/060001.html</a> seems to indicate that 3.10.2 was re-released some time before 2020-01-23 16:16 PST (2020-01-24 00:16 UTC). So <b>if you downloaded QGIS 3.10.2 before that, you should re-download it</b> to not suffer from the bugs of the old library versions.<o:p></o:p></p><p>I don't know why the 3.10.2 was re-released instead of releasing 3.10.3 with the upgraded library versions as suggested in that mailing list thread (<a href="https://lists.osgeo.org/pipermail/qgis-developer/2020-January/059983.html">here</a> and <a href="https://lists.osgeo.org/pipermail/qgis-developer/2020-January/059986.html">here</a>). Releasing it as 3.10.3 would have made it more clear to users, which version they actually downloaded and would have been more in line with semantic versioning concepts. (I dunno whether QGIS aims to follow semantic versioning conventions.)<o:p></o:p></p><p>Kind regards,<br>Raphael<o:p></o:p></p></div></body></html>