Except of one 0.19-specific change, the PR 2630 should be backported before a 0.18.4 release because it fixes 2 issues on installing 0.18.4 over 0.18.x.
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
Re: Back port commits to 0.18 branch
Reference here: #2630 Win installer fixes
Except of this change:It must therefore also be backported to FC 0.18.Code: Select all
+ File /r "${FILES_FREECAD}\resources"
Always add the important information to your posts if you need help. Also see Tutorials and Video tutorials.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
Re: Back port commits to 0.18 branch
Thanks. I see now that the new Windows installer has not yet been backported for FC 0.18. Therefore there is nothing to be backported.
Re: Back port commits to 0.18 branch
looo wrote:ping
kkremitzki wrote:ping
How do you guys feel about creating the 0.18.4 tag?triplus wrote:ping
"fight the good fight"
Re: Back port commits to 0.18 branch
For conda-forge based packages it makes more sense to do something like a 0.19.alpha release using any of the current 0.19.pre builds. These have quite some advantages over the 0.18 builds which rely on the older toolchain and uses qt-webkit.sgrogan wrote: ↑Sat Oct 26, 2019 2:10 pmlooo wrote:pingkkremitzki wrote:pingHow do you guys feel about creating the 0.18.4 tag?triplus wrote:ping
- kkremitzki
- Veteran
- Posts: 2517
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Back port commits to 0.18 branch
Yeah, it looks like it's time.
Re: Back port commits to 0.18 branch
We will just point them to the 0.19_pre.
OK
https://github.com/FreeCAD/FreeCAD/releases/tag/0.18.4
I hope to fill it out by next weekend.
"fight the good fight"
Re: Back port commits to 0.18 branch
Since we're not backporting many commits, we should at lease add a changelog explaining why these minor releases are happening?
We're pointing people to the Known Issues thread but that is pretty static. I think adding bullet point or each commit makes sense.
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
BTW, distrowatch is also following our 0.18 tip
https://repology.org/project/freecad/badges
https://repology.org/project/freecad/badges
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
Well
For the Windows installer of 0.18.4 please assure that you take the latest installer version from the master branch because I recently fixed an issue when installing FC 0.18.x over an existing 0.18.x (This will be the case when users install 0.18.4 over their 0.18.x.)