You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is there a letter v in the branch names, tag names, package names, and version numbers of Nebula Graph and its eco-tools?
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:
The text was updated successfully, but these errors were encountered:
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).
Why is there a letter v in the branch names, tag names, package names, and version numbers of Nebula Graph and its eco-tools?

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:



The text was updated successfully, but these errors were encountered: