We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
参见:https://semver.org
How should I deal with revisions in the 0.y.z initial development phase? The simplest thing to do is start your initial development release at 0.1.0 and then increment > the minor version for each subsequent release.
How should I deal with revisions in the 0.y.z initial development phase?
The simplest thing to do is start your initial development release at 0.1.0 and then increment > the minor version for each subsequent release.
The text was updated successfully, but these errors were encountered:
目前还有一个文件元数据处理的功能没有实现 搞定后就可以进入 0.1 的阶段了
0.0 的版本号用于表示处于开发阶段 随时可能暴毙
Sorry, something went wrong.
好吧,仅作建议。但若不遵守 semver 会造成很多麻烦。
Cargo 也非常建议使用 SemVer,尽管不是硬性指标。
0.x.x 都表示在开发阶段。第三个版本号叫 PATCH version,一般是表示修 bug 的。所以,开发的第一个版本都是从 0.1.0 开始。看你目前的 Release 情况,可能实际上用 0.1.0-nightly-日期 会更好。
0.1.0-nightly-日期
虽说本 repo 不是库而是应用,也可以自定义版本号,如常见的 年份.功能版本.修复版本 等。但与其自定义一套,不如简单拿着 SemVer 来用,避免反复造标准。
年份.功能版本.修复版本
以上,这个 issue 就先 close 吧。
No branches or pull requests
参见:https://semver.org
The text was updated successfully, but these errors were encountered: