Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unnecessary v in branch and version names #4211

Closed
randomJoe211 opened this issue Apr 26, 2022 · 2 comments
Closed

Unnecessary v in branch and version names #4211

randomJoe211 opened this issue Apr 26, 2022 · 2 comments

Comments

@randomJoe211
Copy link
Contributor

randomJoe211 commented Apr 26, 2022

Why is there a letter v in the branch names, tag names, package names, and version numbers of Nebula Graph and its eco-tools?
image

Making v part of the version number does not make sense, neither logically nor grammatically. For example, when we refer to a specific version of Nebula Graph, we don't write "Nebula Graph version v3.0.2", but just "Nebula Graph version 3.0.2" or simply "Nebula Graph 3.0.2".

And we don't have a "v" series, such as v-3.0.2 or 3.0.2-v.

Cases in the database industry are:
C2A8D899-AC77-4ae9-A5F9-F51273DC545D
65D21E7B-8481-4213-843F-A9F5108907CB
0D918CB1-49BD-4c45-B049-C2E436F09B81

@randomJoe211
Copy link
Contributor Author

@Sophie-Xie

@Sophie-Xie
Copy link
Contributor

Thanks.
We modified the branch name to avoid misuse of tag and branch, and to ensure that the z version of x.y is on a branch. But we do not plan to change the tag name, in order to keep it consistent with the past. Every community has different definition about tag name, such as k8s (with v).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants