<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I currently use 2.18 to work around some bugs in 3.0, and it is
possible even with the difference in project file formats as there
is enough compatibility. Although lately the CRS translation has
been broken when opening a 3.0 project in 2.18 and I have been
told there is no guaranteed backwards compatibility.</p>
<p>Personally I would advocate for engineering a little bit of
backporting into 2.18 to allow it to recognise the CRS from the
project file which is currently challenging, as it seems to be
able to recognise everything else well enough to be able to view a
map on opening the project file and I have done this many times
while running the development masters on my live maps during the
past year or so. <br>
</p>
<p>The main thing that is not translated is layer styles and whilst
this is a big part at the moment I can work around that well
enough to not make a big issue out of that which would probably be
a much more significant effort to backport.<br>
</p>
<p>As it stands, 2.18 will be maintained as the last version LTR for
many years yet until 3.2 is released and we haven't even got to
3.0 yet. In fact I do have some doubt that the 3.0 release date is
going to be met (but of course I have no real insight into the
process so it is just an informed opinion at best)<br>
</p>
<br>
<div class="moz-cite-prefix">On 05/12/17 05:06, Larry Shaffer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+nQOR-9ji=1q-4DdYfgdTwGRA8mCoUmjC-eTA+O51YumWAP-A@mail.gmail.com">
<div dir="ltr">Hi,
<div><br>
</div>
<div>On Mon, Dec 4, 2017 at 2:00 AM, Richard Duivenvoorde <span
dir="ltr"><<a href="mailto:rdmailings@duif.net"
target="_blank" moz-do-not-send="true">rdmailings@duif.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><span class="gmail-">On
04-12-17 01:01, Nathan Woodrow wrote:<br>
> Hey all,<br>
><br>
> Just wanted to see how everyone would feel if I was
thinking about<br>
> backporting the crash handler we have in QGIS 3 back
into 2.18. <br>
</span></blockquote>
<div><br>
</div>
<div>+ 1 from me.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><span class="gmail-"></span>I
think it is a good idea...<br>
<br>
As you say, 2.18 will be here for some time (especially for
educational<br>
and governmental institutions probably, all running
windows).<br>
</blockquote>
<div><br>
</div>
<div>This is certainly true and a clear justification for the
backport. Those enterprises may keep using QGIS 2.18,
possibly up to a year from now (with respect to next LTR
release and adoption), or longer. Horrifying to consider,
but at least this crash handler will help.</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Indeed then people can at
least report back something (as I think our<br>
normal stacktrace-sources: Linux devs, will probably move on
to 3.x).<br>
<br>
While it looks like if we want to say that QGIS ever crashes
on Windows,<br>
maybe name it Windows or Data Crash Handler ;-) ....<br>
<br>
Needs to be tested thoroughly though, as it is a new
'feature' in LTR...<br>
Is it testable?<br>
<br>
Regards,<br>
<br>
Richard</blockquote>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr"><br>
Larry Shaffer<br>
Dakota Cartography<br>
Black Hills, South Dakota<br>
----------------------------------<br>
Boundless Desktop and QGIS Support/Development<br>
Boundless Spatial - <a href="http://boundlessgeo.com"
target="_blank" moz-do-not-send="true">http://boundlessgeo.com</a><br>
<a href="mailto:lshaffer@boundlessgeo.com"
target="_blank" moz-do-not-send="true">lshaffer@boundlessgeo.com</a></div>
</div>
</div>
<br>
<div class="gmail_quote">On Mon, Dec 4, 2017 at 4:21 AM, Tom
Chadwin <span dir="ltr"><<a
href="mailto:tom.chadwin@nnpa.org.uk" target="_blank"
moz-do-not-send="true">tom.chadwin@nnpa.org.uk</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">A huge
+1 from me - as a Windows user, it's frustrating not to be
able to<br>
investigate the occasional times PyQGIS causes a Windows
minidump.<br>
<br>
Tom<br>
<br>
<br>
<br>
-----<br>
Buy Pie Spy: Adventures in British pastry 2010-11 on
Amazon<br>
--<br>
Sent from: <a
href="http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://osgeo-org.1560.x6.<wbr>nabble.com/QGIS-Developer-<wbr>f4099106.html</a><br>
<div class="HOEnZb">
<div class="h5">______________________________<wbr>_________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org"
moz-do-not-send="true">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a></div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>