Back port commits to 0.18 branch

Here's the place for discussion related to coding in FreeCAD, C++ or Python. Design, interfaces and structures.
looo
Posts: 2749
Joined: Mon Nov 11, 2013 5:29 pm

Re: Back port commits to 0.18 branch

Postby looo » Mon Jul 22, 2019 7:06 am

looking at the commit history of the cmake-file, it seems like more work is needed to get qtwebengine suport in 0.18. Qtwebkit with qt5.9 from conda-forge is not really an option.

But in my eyes backporting these commits doesn't make too much sense, as master is currently quite stable and the latest 0.19 build is working with qtwebengine... Also I think if you want to work on a bundle from conda packages for windows using latest master makes more sense (weekly builds from freecad/label/dev)


So:
looo wrote:
Sat Jul 20, 2019 9:01 am
Yes, moving 0.18.3 to qt5.9 looks quite obvious to me.
doesn't look that obvious anymore :D . So I will stay with qt5.6 for 0.18.3.
User avatar
sgrogan
Posts: 5252
Joined: Wed Oct 22, 2014 5:02 pm

Re: Back port commits to 0.18 branch

Postby sgrogan » Mon Jul 22, 2019 8:35 pm

looo wrote:
Mon Jul 22, 2019 7:06 am
doesn't look that obvious anymore :D . So I will stay with qt5.6 for 0.18.3.
OK sounds like a good plan.
See Here: https://forum.freecadweb.org/viewtopic.php?f=42&t=37906
User avatar
hholgi
Posts: 18
Joined: Wed Sep 19, 2018 9:35 am
Location: Gütersloh, Germany

Re: Back port commits to 0.18 branch

Postby hholgi » Tue Jul 23, 2019 7:55 am

Hello,
Maybe only a known hint: The new 018.3 portable Version result in a "WS.Reputation.1" warning from "Symantec Endpoint Protection".
The 018.2 did not create this warning …
MTB racing service for TR in www.rsv-guetersloh.de; RC flight model in www.moewe-delbrueck.de
Actual FreeCad is: 0.18.3 on Win10
Jee-Bee
Posts: 1942
Joined: Tue Jun 16, 2015 10:32 am
Location: Netherlands

Re: Back port commits to 0.18 branch

Postby Jee-Bee » Tue Jul 23, 2019 8:23 am

hholgi wrote:
Tue Jul 23, 2019 7:55 am
Hello,
Maybe only a known hint: The new 018.3 portable Version result in a "WS.Reputation.1" warning from "Symantec Endpoint Protection".
The 018.2 did not create this warning …
fill in this one: https://submit.symantec.com/false_positive/
User avatar
hholgi
Posts: 18
Joined: Wed Sep 19, 2018 9:35 am
Location: Gütersloh, Germany

Re: Back port commits to 0.18 branch

Postby hholgi » Tue Jul 30, 2019 6:07 am

Jee-Bee wrote:
Tue Jul 23, 2019 8:23 am
fill in this one: https://submit.symantec.com/false_positive/
Maybe someone other did this....
Since yesterday the warning is not longer shown .... :mrgreen:
MTB racing service for TR in www.rsv-guetersloh.de; RC flight model in www.moewe-delbrueck.de
Actual FreeCad is: 0.18.3 on Win10
triplus
Posts: 8605
Joined: Mon Dec 12, 2011 4:45 pm

Re: Back port commits to 0.18 branch

Postby triplus » Sun Aug 18, 2019 5:41 pm

looo wrote:
Sat Jul 20, 2019 9:01 am
But as said I need come help from @triplus as I have no idea about the upload-scripts.
I see you have figured it out. A month back, when i was working on this, there was still a glitch somewhere, when it comes to deploying to latest, and hence i need to figure that out in the following days. After hopefully deployment to latest will happen automatically.
Syres
Posts: 325
Joined: Thu Aug 09, 2018 11:14 am

Re: Back port commits to 0.18 branch

Postby Syres » Sun Aug 25, 2019 8:12 am

Not sure if 0.18.4 is being considered but if so, this maybe relevant https://forum.freecadweb.org/viewtopic. ... 20#p329120

EDIT: The commit is https://github.com/FreeCAD/FreeCAD/commit/6a8f6e2a
dubstar-04
Posts: 380
Joined: Mon Mar 04, 2013 8:41 pm
Location: Manchester, UK
Contact:

Re: Back port commits to 0.18 branch

Postby dubstar-04 » Wed Aug 28, 2019 7:44 pm

It would be good to get this included if there will be another 18.x release.

https://github.com/FreeCAD/FreeCAD/pull/2434
triplus
Posts: 8605
Joined: Mon Dec 12, 2011 4:45 pm

Re: Back port commits to 0.18 branch

Postby triplus » Mon Sep 02, 2019 3:31 pm

triplus wrote:
Sun Aug 18, 2019 5:41 pm
looo wrote:
Sat Jul 20, 2019 9:01 am
But as said I need come help from @triplus as I have no idea about the upload-scripts.
I see you have figured it out. A month back, when i was working on this, there was still a glitch somewhere, when it comes to deploying to latest, and hence i need to figure that out in the following days. After hopefully deployment to latest will happen automatically.
Note that stable AppImage/DMG files will now deploy to latest. I added the support yesterday. On Mac, GitHub API rate limit issue was detected. I managed to resolve it today, by including the authentication.

P.S. There is a section in .travis.yml file. Whenever needed, it can be used for setting the tag manually:

Code: Select all

  - # Uncomment to manually set the tag name
  - # DEPLOY_RELEASE_STABLE="0.18.3"
chrisb
Posts: 17598
Joined: Tue Mar 17, 2015 9:14 am

Re: Back port commits to 0.18 branch

Postby chrisb » Mon Sep 02, 2019 3:53 pm

Thanks! I was already pleasantly surprised that I could update twice during the last two days. This is highly appreciated in these times of the big merge.