Back port commits to 0.18 branch

[Kunda1]

Good point openBrain

[openBrain]

Good point openBrain

Thanks. Not that I'm proud of these commits, but they looks to me very little risky, while with a potential high gain regarding forum threads we'll have when Inkscape 1.0 will be released and adopted.

[Kunda1]

• git commit 04641657d040c0fe fixes issue #4233 - Access violation and file corruption on undo duplicate sketch
• git commit 9f2401dd4e6410b8 fixes [Draft] ImportDXF 0.18 Bug upgrading from 0.16

[uwestoehr]

This one should be backported in my opinion: https://github.com/FreeCAD/FreeCAD/pull/2909

[chrisb]

Is there a good reason why exactly this should be backported? Most users of Path workbench seem to use 0.19 anyway - for good reasons.

[uwestoehr]

Is there a good reason why exactly this should be backported? Most users of Path workbench seem to use 0.19 anyway - for good reasons.

Because our latest stable release should get all known bugfixes. Especially new users start with the stable version and not an unreleased 0.19.

[chrisb]

Because our latest stable release should get all known bugfixes.

Was there a decision made on this?

[uwestoehr]

Was there a decision made on this?

The branch maintainer has to decide, I can only make a proposal.
I don't know who the 0.18 maintainer is.

[chrisb]

No, I mean on the general strategy of having all bugfixes backported. That seems rather uncommon. New releases usually bring new features and bugfixes. Backports are made for more or less critical bugs.

[sgrogan]

I don't know who the 0.18 maintainer is.

Its wmayer, yorik, and the WB maintainers.
Historically only critical bug fixes would be backported, like crashes!
As the FreeCAD distribution capability has increased more "usability" bugfix backports have been excepted. I would note that wmayer is the OP for this thread.

When the binaries are built/released is a loose collaboration of the packagers.

@kkremitzkii
@looo
@hobbes
@sgrogan