Appimage and dmg are uploaded to dropbox[1]. I used the last 0.18 commit[2].
[1] https://www.dropbox.com/sh/tcpg7xrvjdun ... Oteia?dl=0
[2] https://github.com/FreeCAD/FreeCAD/comm ... f3febea0d2
Appimage and dmg are uploaded to dropbox[1]. I used the last 0.18 commit[2].
I am not sure how to handle this. We have an 0.18.16111 which is ahead of the release 0.18.16093?
I think what he needs is the "0.19_pre" tag and update to the build system so that it would produce 0.19 versions in the about dialog and other related places. About the additional commits I would not complicate, just backport them and make a final 0.18 when ever all the things are ready. In a month or two everyone will want to be on 0.19_pre anyway
Almost.saso wrote: ↑Sat Mar 16, 2019 12:46 pm I think what he needs is the "0.19_pre" tag and update to the build system so that it would produce 0.19 versions in the about dialog and other related places. About the additional commits I would not complicate, just backport them and make a final 0.18 when ever all the things are ready. In a month or two everyone will want to be on 0.19_pre anyway
You are as usual ahead of me.looo wrote: ↑Sat Mar 16, 2019 3:22 pm Btw.: Conda-forge freecad-feedstock will get automated PR's for everyone new tag. I now used the current 0.18 tag. I will provide the appimage and dmg for the release from local builds using the specific commit and not the tag. Once a new tag has the backports included we can also use the builds from the ci's.
So it would be good if wmayer would backport those commits that he sees should be backported, this one could maybe also be a candidate https://github.com/FreeCAD/FreeCAD/pull/2019
@looo, can I upload these to the releases pages as release candidates (RC)?