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.
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.
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.
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)
On 05/12/17 05:06, Larry Shaffer wrote:
Hi,
On Mon, Dec 4, 2017 at 2:00 AM, Richard Duivenvoorde
<rdmaili...@duif.net <mailto:rdmaili...@duif.net>> wrote:
On 04-12-17 01:01, Nathan Woodrow wrote:
> Hey all,
>
> Just wanted to see how everyone would feel if I was thinking about
> backporting the crash handler we have in QGIS 3 back into 2.18.
+ 1 from me.
I think it is a good idea...
As you say, 2.18 will be here for some time (especially for
educational
and governmental institutions probably, all running windows).
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.
Indeed then people can at least report back something (as I think our
normal stacktrace-sources: Linux devs, will probably move on to 3.x).
While it looks like if we want to say that QGIS ever crashes on
Windows,
maybe name it Windows or Data Crash Handler ;-) ....
Needs to be tested thoroughly though, as it is a new 'feature' in
LTR...
Is it testable?
Regards,
Richard
Larry Shaffer
Dakota Cartography
Black Hills, South Dakota
----------------------------------
Boundless Desktop and QGIS Support/Development
Boundless Spatial - http://boundlessgeo.com
lshaf...@boundlessgeo.com <mailto:lshaf...@boundlessgeo.com>
On Mon, Dec 4, 2017 at 4:21 AM, Tom Chadwin <tom.chad...@nnpa.org.uk
<mailto:tom.chad...@nnpa.org.uk>> wrote:
A huge +1 from me - as a Windows user, it's frustrating not to be
able to
investigate the occasional times PyQGIS causes a Windows minidump.
Tom
-----
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
Sent from:
http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
<http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html>
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org <mailto:QGIS-Developer@lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
Unsubscribe:
https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
