Versions, git tags and branches

[vitoyucepi]

Why for version v2.0.0 at the same time exists

• PR Liquidsoap 2.0.0 #1878. Will this PR ever merged into v2.0.0-rc1?
• Branch https://github.com/savonet/liquidsoap/tree/v2.0.0
• Tag https://github.com/savonet/liquidsoap/releases/tag/v2.0.0

I've never seen this before.
Maybe there should branches

• main as a center of new development.
• 2.0 as a branch for tags 2.0.0, 2.0.1, etc.
  This branch provides support for versions 2.0.x.
  Commits from main can be cherry-picked into this branch.

Each tag will be set once and never change.
If something nasty happens it's ok to push a new tag after a broken one.
There can be also pre-release tags: alpha, beta, rc.

This bothers me because from time to time I want to download release artifacts for 2.0.0. Sometimes there's no release artifacts.

[toots]

I understand that this is confusing. We have the CI automatically create a release, release tag and upload assets to the release for any given branch named v..., which is what creates the tags.

We need a PR to trigger the whole CI process. It will never get merged but it shows us the full list of changes since the previous release.

I'll see about simplifying it but there's a lot of machinery involved with building assets for all the target that we support and etc.

The source of truth for releases should be the release tab here: https://github.com/savonet/liquidsoap/releases