Release of 0.18
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
- kkremitzki
- Veteran
- Posts: 2509
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Release of 0.18
I have a 0.18~pre package available on my personal PPA at https://launchpad.net/~kkremitzki/+archive/ubuntu/ppa ready for testing. A few notes:
* if you have freecad-stable PPA you'll have to remove it as that version has the epoch set to 1 (i.e. the version starts with 1:) so that makes 1:0.17 > 0.18
* the start workbench is broken because the debian package does not install .fcstd examples, sudo mkdir /usr/share/freecad/examples to get around this for now. If we included the .py files required to generate the example files we could include them with Debian, I think.
* the default version is python 2, if you want to install python 3 do sudo apt install freecad-python3 libfreecad-python3-0.18. (eventually it'll just be sudo apt install freecad-python3, that's a packaging bug and I'll edit this later.)
* if you want to switch between versions, incl. after doing the above step to install python 3, run sudo update-alternatives --config freecad. This will give an interactive prompt to select the Python 3 version, after this then /usr/bin/freecad, freecadcmd, and the desktop launcher both point to the Python 3 version.
Please try it out and report any bugs!
* if you have freecad-stable PPA you'll have to remove it as that version has the epoch set to 1 (i.e. the version starts with 1:) so that makes 1:0.17 > 0.18
* the start workbench is broken because the debian package does not install .fcstd examples, sudo mkdir /usr/share/freecad/examples to get around this for now. If we included the .py files required to generate the example files we could include them with Debian, I think.
* the default version is python 2, if you want to install python 3 do sudo apt install freecad-python3 libfreecad-python3-0.18. (eventually it'll just be sudo apt install freecad-python3, that's a packaging bug and I'll edit this later.)
* if you want to switch between versions, incl. after doing the above step to install python 3, run sudo update-alternatives --config freecad. This will give an interactive prompt to select the Python 3 version, after this then /usr/bin/freecad, freecadcmd, and the desktop launcher both point to the Python 3 version.
Please try it out and report any bugs!
Re: Release of 0.18
I vote for closing https://www.freecadweb.org/tracker/view.php?id=3522
Its most likely a graphics driver issue..
I have been able to reproduce it in 0.16, 0.17 and 0.18.
But today when i booted it wont show up again, FreeCAD app images have not changed..
Probably related to other "incorrect rendering of thin walled objects issues", like this:
Its most likely a graphics driver issue..
I have been able to reproduce it in 0.16, 0.17 and 0.18.
But today when i booted it wont show up again, FreeCAD app images have not changed..
Probably related to other "incorrect rendering of thin walled objects issues", like this:
Re: Release of 0.18
Closed.fosselius wrote: ↑Fri Jan 18, 2019 10:13 am I vote for closing https://www.freecadweb.org/tracker/view.php?id=3522
Its most likely a graphics driver issue..
A Sketcher Lecture with in-depth information is available in English, auf Deutsch, en français, en español.
Re: Release of 0.18
chrisb wrote: ↑Fri Jan 18, 2019 10:49 amClosed.fosselius wrote: ↑Fri Jan 18, 2019 10:13 am I vote for closing https://www.freecadweb.org/tracker/view.php?id=3522
Its most likely a graphics driver issue..
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: Release of 0.18
So I want to apologize for all the emails and noise everyone has been receiving from me kicking the tires, dusting, and re-arranging the furniture over in Crowdin. I even got an earful from NormandC about it, imagine that (sincere apologies, buddy). I'm also getting ready to send more commits to github, so apologies for that noise as well. Yes, it's a bigger task than I imagined but I wanted to be thorough and figure out a workflow that will make it easier for everyone.
One way to do it properly is to have crowdin admins and proofreaders stay on top of issues that are being created by translators. (Ugh, not another guideline and job!) Yes, this is actually easier than you think if you know how to use the Crowdin UI. I've started a WIP wiki page that has such tips called Crowdin Administration. Also several tickets have been opened issue #3715, issue #3777, and issue #3654. I want to send a shoutout to the active FreeCAD users who are also managing Crowdin. Thank you for dedicating time to this. We're all doing good work.
I'd like to also say something about the translators. Beside being awesome (most of them), many of them are on the 'frontlines' and they are akin to QA testers. Many typos and even bugs have been discovered through their help. So just wanted to acknowledge I realize the importance of translators on the health of a project, their feedback is important.
Now, I have been brain-dumping over at https://forum.freecadweb.org/viewtopic.php?f=10&t=33475 trying to understand what is going on with why we're seeing all these obsolete strings, I call it garbage in the Crowdin UI. My current conclusion is that the issue may be stemming from our translation workflow. Something in how we update our own translation files initially before we add to Crowdin and after we pull translations back in to Crowdin (yea, I narrowed it down alright ). I need some help though because I'm not sure why we're doing certain things. Thus I documented those questions in the thread. Any help would be appreciated.
Edit: I'd like to send more translation fixes to https://github.com/FreeCAD/FreeCAD/pull/1912 but Travis is complaining about my l33t c++ skillz. Question: once that PR is fixed, what would the preferable course of action be? squash the fixed commits down ? Accepting the PR as it is? Or just keep pushing commits to it?
One way to do it properly is to have crowdin admins and proofreaders stay on top of issues that are being created by translators. (Ugh, not another guideline and job!) Yes, this is actually easier than you think if you know how to use the Crowdin UI. I've started a WIP wiki page that has such tips called Crowdin Administration. Also several tickets have been opened issue #3715, issue #3777, and issue #3654. I want to send a shoutout to the active FreeCAD users who are also managing Crowdin. Thank you for dedicating time to this. We're all doing good work.
I'd like to also say something about the translators. Beside being awesome (most of them), many of them are on the 'frontlines' and they are akin to QA testers. Many typos and even bugs have been discovered through their help. So just wanted to acknowledge I realize the importance of translators on the health of a project, their feedback is important.
Now, I have been brain-dumping over at https://forum.freecadweb.org/viewtopic.php?f=10&t=33475 trying to understand what is going on with why we're seeing all these obsolete strings, I call it garbage in the Crowdin UI. My current conclusion is that the issue may be stemming from our translation workflow. Something in how we update our own translation files initially before we add to Crowdin and after we pull translations back in to Crowdin (yea, I narrowed it down alright ). I need some help though because I'm not sure why we're doing certain things. Thus I documented those questions in the thread. Any help would be appreciated.
Edit: I'd like to send more translation fixes to https://github.com/FreeCAD/FreeCAD/pull/1912 but Travis is complaining about my l33t c++ skillz. Question: once that PR is fixed, what would the preferable course of action be? squash the fixed commits down ? Accepting the PR as it is? Or just keep pushing commits to it?
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: Release of 0.18
Don't worry too much about it, but if it becomes very long, you can also indeed squash it and make another PR. That's indeed cleaner as we won't need the intermediary commits.
Indeed there is quite a lot of discussion coming from crowdin, not really sure how best to integrate all this...
Indeed there is quite a lot of discussion coming from crowdin, not really sure how best to integrate all this...
- kkremitzki
- Veteran
- Posts: 2509
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Release of 0.18
Tomorrow I'm going to bump the daily builds PPA to 0.18~beta2 in advance of the release. This is going to be a big change which will bring the PPA packaging in line with Debian (splitting out the monolithic freecad package into several) and provide side-by-side Python 2 & 3 support which can be switched between via sudo update-alternatives --config freecad-daily. By default if you sudo apt install freecad-daily I have it set to grab freecad-daily-python3 package, so if you want to switch first sudo apt install freecad-daily-python2. You could also just execute the previous command by itself, the freecad-daily package will just be a meta-package that is the equivalent of running sudo apt install freecad-daily-python3 freecad-daily-common freecad-daily-runtime libfreecad-daily-python3-0.18.
Once this is done and bugs ironed out then the stable PPA should be ready as soon as a release happens.
BTW, this is only for Ubuntu 18.04+
Once this is done and bugs ironed out then the stable PPA should be ready as soon as a release happens.
BTW, this is only for Ubuntu 18.04+
Re: Release of 0.18
What is the status of:
https://www.freecadweb.org/tracker/view.php?id=2461
https://forum.freecadweb.org/viewtopic.php?f=10&t=20258
as its a "known" issue with occt, maybe close and open new ticket that correctly describes the "real" issue, if its not resolved?
Re: Release of 0.18
I tested this with OCCT 7.2 and for me an error message is raised when I only add the sections and press OK but the application does not crash. However, for my 7.2 build (on Windows) I have enabled the OCCT exception mechanism which avoids many possible segfaults. So, with a standard 7.2 build it may crash, too.fosselius wrote: ↑Sun Jan 20, 2019 8:06 pm
What is the status of:
https://www.freecadweb.org/tracker/view.php?id=2461
https://forum.freecadweb.org/viewtopic.php?f=10&t=20258
as its a "known" issue with occt, maybe close and open new ticket that correctly describes the "real" issue, if its not resolved?
But when I also choose the Ruled surface option it works. The resulting shapes doesn't look very nice but it works.
Re: Release of 0.18
Ok, this might not be an biggie, so i will just put it here, the "thin wall" rendering issue for the lego house mentioned above,
I found that the issue exists on 0.17 and 0.18 and that no zoom, rotation etc resolves it.
However, pressing the view fit button always resolves it. I guess it "resets" the scene in some way??
Have tried to find in the code where things happen, but have not yet located it.
It feels like the "default" scene setup renders at object depth - 1
I found that the issue exists on 0.17 and 0.18 and that no zoom, rotation etc resolves it.
However, pressing the view fit button always resolves it. I guess it "resets" the scene in some way??
Have tried to find in the code where things happen, but have not yet located it.
It feels like the "default" scene setup renders at object depth - 1
Code: Select all
Gui.SendMsgToActiveView("ViewFit")
- Attachments
-
- thinWallIssue.gif (318.95 KiB) Viewed 1836 times