test/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2024-12-05 05:18:52 +08:00
Code Issues Actions 14 Packages Projects Releases Wiki Activity
a63d832772
milvus/RELEASE.md
Jin Hai 23e0816baa
Fix Markdown format (#1485) 
* 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>
2020-03-03 00:25:22 +08:00

788 B
Raw Blame History

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.

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.