During the last community call, I've briefly mentioned this, but I wanted
to point out an approach that might be very simple. Hence the reiteration.
In Github, I find it hard to find the code state / commit that is an
official release of a Jitsi project. The continuous integration creates
tags and releases for every successful build. This muddies the water
A pragmatic approach could be to _not_ have CI create a Github "release"
(but only use "tags" for CI). If you'd only use Github releases for
something that you consider to be a stable release, it becomes super easy
to identify what code belongs to what release.
This in turn allows me to easily base my downstream projects on your stable
code, instead of a random tagname (which is what I've been doing so far).
What do you think?