We could, but I think it causes problems. Naming the file something like 0.18-dev would make the link more stable but it looses all versioning information. It's a pretty big package and I don't want to continuously download the same version everyday. Maybe this is mitigated by .zsync with the AppImages but this is probably no more user friendly.
Unfortunately the text is at the bottom https://github.com/FreeCAD/FreeCAD/rele ... g/0.18_pre, you need to scroll down.
The Github/releases is not engineered for daily(developer) builds. we could switch to a point release vs. backport release strategy for released builds.Kunda1 wrote: ↑Mon Nov 12, 2018 2:56 pmOne of the problems for FC right now when we direct people to the developmental released page on GitHub, is that people are looking at the amount of commits that have changed since the release
of 0.18_pre whichh is inaccurate instead of realizing that developmental builder generated daily. Because we're not using GitHub release methodology the way it was engineered to be. And that is okay. But it is confusing. It's been like this for a while and I'm just choosing to try to tackle it now
We need a way to update the links at deploy time.