Add and keep up-to-date a tag pointing to the most recent stable release?

[blipp]

I am reviewing the wiki page https://github.com/rosenpass/rosenpass/wiki/Compilation-and-Installation

With such a tag, we could just point people to that tag instead of telling them to figure out what the most recent release is.

Do you think this is a good idea? Are there unpleasant side effects?

[ilka-schulz]

I totally understand the need for that! I find that many FOSS projects could need this, tbh...

Some use Git Flow which can be used in a way where your main branch only sees releases and all other commits are not merged into main until there is a release. I personally love that in combination with Continuous Deployment where each branch (e.g. main, testing, develop) corresponds to a deployment environment.

Using a branch name rather than a tag name is probably a wiser decision (e.g. latest, major, etc.) because it can move every time a new version get released. A tag would need to be deleted and re-created.

I am not entirely sure how well this would correspond to manual work and error-proneness. I am usually using GitLab and I know for sure that you can do tests in CI which check that a new release can only be done if the mentioned branch name is on the same commit.