Therefore "continuous release/tag" gets deleted and recreated each time, before deploying, but that still doesn't explain this to me:
Release build (11) @probonopd probonopd released this on 21 Oct 2018
FreeCAD 0.18 @sgrogan sgrogan released this 28 days ago · 18 commits to releases/FreeCAD-0-18 since this release
Where does the difference come from?
There is not really a difference between 0.18.1 and 0.19, except following the Symantec Versioning rules.
I would say there is? Point release is a release with some additional backports and mostly fixes? People should always be directed to the latest point release binaries, perceiving them as a release binaries? The problem i have now is where exactly to deploy 0.18.1 binaries? As if i deploy them to 0.18.1, then there will still be an older set of binaries located at 0.18. When it comes to AppImage, update information of AppImage, downloaded from 0.18, will point to 0.18, and not to 0.18.1. If there would be a "release" and "continuous". All releases would have update information pointed to "release", and all development oriented AppImages to "continuous", just like the PPA updating works. Latest point release binaries would be moved to 0.18, before we would start deploying next FreCAD release binaries (next year). All existing release/development oriented AppImages out there would therefore always get updated to latest release/development FreeCAD version made available.
Developer builds get deployed to 0.xx_pre
Yes, for now i will deploy to 0.19_pre.
Release builds get deployed to the releases matching the tag they're built against.
Here i would rather deploy point releases to FreeCAD 0.18. And not to have a plethora of point release binaries all over the GitHub releases page. And worry on how to update the whole matrix, once some (packaging) issue gets reported and to fix the issue all binaries from release and point releases would need to get updated. At minimum therefore each point release should have a note and a link, explaining latest point release binaries are located at 0.18?
Today i signed in the Travis. As a member of FreeCAD organization i have access to an overview, could trigger a build from Travis ... For settings i don't have sufficient permissions. People that have access to settings, can set things like environment variables, to determine on where exactly to deploy. On the other hand, there most likely are some secure variables in there and therefore it's a good thing, only a limited set of people has access. In addition i can modify the deploy related variables from the .yml file directly, and that should suffice for completing this task. Today i managed to get most of the work done and i am rather optimistic that tomorrow things should start to move forward a bit.
P.S. One question, are you currently creating Conda Windows builds with a script? If yes, that could likely get automated in the future.