Tag new release or delete tags?

[ottok]

Hi,

This repository has two release tags. Latest v6.1.0-alpha is from 2022.

TiUP depends on this module based on commit id, not tag (github.com/pingcap/kvproto v0.0.0-20230331024443-349815129e6d).

Having two tags but not using tags is confusing. Is your plan to do any new release tags? Or should you delete the existing tags to make it explicit that this repository does not tag any releases (similar to failpoint), and all consumers should just depend on git HEAD or a commit of their choice?

Related: #280

CC: @dveeden

[dveeden]

I've asked the team.

[ottok]

There is also the cargo.toml that advertises version 0.0.2 (yes #280 is not completed and this package was actually not released officially yet):

[package]
name = "kvproto"
version = "0.0.2"
keywords = ["TiKV"]
edition = "2018"
build = "build.rs"

I didn't find any other files on the branch master that would define versions.

However I see there are branches release-* with the latest being release-7.4 from September 2023. TiUP depends on commit 3498151 that only exists on the master branch. So perhaps doing a version 7.5 release now, or even 8.0 would be appropriate?

The version I uploaded to Debian is based on git tag 6.1.0~alpha from 2022, and is so old that I had to patch it to make it compatible with the protobuffer version in Debian.

If you decide to not do any releases anymore, please remove the versioning and mention in the README explicitly that anyone using this should be using the git HEAD and not any releases.