mirror of
https://gitee.com/milvus-io/milvus.git
synced 2024-11-30 19:08:30 +08:00
23e0816baa
* Fix #839 and improve the code quality Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix compiling error and building threads number Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown quality Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown quality Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown quality Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown format Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown format Signed-off-by: JinHai-CN <hai.jin@zilliz.com> * Fix Markdown format Signed-off-by: JinHai-CN <hai.jin@zilliz.com>
18 lines
788 B
Markdown
18 lines
788 B
Markdown
# Milvus Release Methodology and Criterias
|
|
|
|
## Release methodology
|
|
|
|
Milvus releases are packages that have been approved for general public release, with varying degrees of caveat regarding their perceived quality or potential for change.
|
|
They are stable releases intended for everyday usage by developers and non-developers.
|
|
|
|
Project versioning follows the specification of [Semantic Versioning 2.0.0](https://semver.org/).
|
|
|
|
## Release criteria
|
|
|
|
- Milvus core test code coverage must be at least 90%.
|
|
- Reported bugs should not have any critical issues.
|
|
- All bugs, new features, enhancements must be tested.
|
|
- All documents need to be reviewed with no broken link.
|
|
- Pressure testing, stability testing, accuracy testing and performance testing results should be evaluated.
|
|
|