Back port commits to 0.18 branch
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Back port commits to 0.18 branch
https://github.com/FreeCAD/FreeCAD/pull ... a97d283ead
Important Qtwebengine fix. Please merge and backport.
Important Qtwebengine fix. Please merge and backport.
Re: Back port commits to 0.18 branch
Added both fixes and also: https://github.com/FreeCAD/FreeCAD/comm ... a236dd1331
Re: Back port commits to 0.18 branch
time for a 0.18.3 release?
Re: Back port commits to 0.18 branch
Can I make a suggestion regarding this? Would it be possible to have the instructions ready along with all platform downloads ready before releasing? v0.18.2 was 'Under Construction' for some time after 0.18.2 was tagged. A tag will show up on the Github RSS feed and API, which some downstream packagers query automatically. It reflects better on us and causes less confusion downstream. Thoughts?
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Back port commits to 0.18 branch
May I suggest
commit 332bfb5052a2f7d45c0683866eba79bf2807d22f
for backport. It alleviates phantom paths occurring in PathWB.
Thanks,
Russell
commit 332bfb5052a2f7d45c0683866eba79bf2807d22f
for backport. It alleviates phantom paths occurring in PathWB.
Thanks,
Russell