Hi,

the CI automation is reworked as part of #853 and #835 (<< notice the numbers? nice coincidence)

My supposed way of handling releases is this:

• Release-Tags: all tags starting with an "r" are built and released with their version number (from .pro file)
• Release-Latest: the tag "latest" is built, too (when moved to a new release)
• Pre-Releases: all branches are built on push, and released with their name marked as "prerelease". If that is too much build time, it could be restricted to the master branch.

Whenever a tag/branch is moved, the old release for that name is replaced. Since the release-tags "rx_x_x" stay, they

Driving thoughts:

• simple flow in automation (one flow, one task. Not mixing release & latest)
• automated builds of intermediate development acessible to non-building users

@corrados is that acceptable?
@corrados do you need the "latest" files to have the "latest" filenames?
@corrados shall pull-requests also build (Pre-Release)?