From 1ec4494cb1ef309002b48a6b6be4e07d68c9d5fd Mon Sep 17 00:00:00 2001 From: peefy Date: Wed, 29 Nov 2023 10:53:39 +0800 Subject: [PATCH] chore: update release policy headers Signed-off-by: peefy --- docs/community/release-policy/kcl.md | 2 +- versioned_docs/version-0.7.0/community/release-policy/kcl.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/community/release-policy/kcl.md b/docs/community/release-policy/kcl.md index 0c68b108..5772bf49 100644 --- a/docs/community/release-policy/kcl.md +++ b/docs/community/release-policy/kcl.md @@ -11,7 +11,7 @@ The KCL project version release strategy is as follows: - Release Process: Before releasing a new version, rigorous testing and review are conducted to ensure the quality of the new version. After finalizing the release and completing the testing, the source code, binaries, and images of the new version will be published on Github, along with detailed documentation and usage guides. - Version Support: Long-term support will be provided for the latest version, including bug fixes and security updates. Limited support will be provided for older versions, with fixes only done when necessary. -## 发布流程与规则 +## Release Process and Rules - Feature Development: Main branch development, branch releases, block user issues, critical bugs, security vulnerabilities, and high-priority fixes. It is given higher priority over general feature development and should be completed within a week. Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months. diff --git a/versioned_docs/version-0.7.0/community/release-policy/kcl.md b/versioned_docs/version-0.7.0/community/release-policy/kcl.md index 0c68b108..5772bf49 100644 --- a/versioned_docs/version-0.7.0/community/release-policy/kcl.md +++ b/versioned_docs/version-0.7.0/community/release-policy/kcl.md @@ -11,7 +11,7 @@ The KCL project version release strategy is as follows: - Release Process: Before releasing a new version, rigorous testing and review are conducted to ensure the quality of the new version. After finalizing the release and completing the testing, the source code, binaries, and images of the new version will be published on Github, along with detailed documentation and usage guides. - Version Support: Long-term support will be provided for the latest version, including bug fixes and security updates. Limited support will be provided for older versions, with fixes only done when necessary. -## 发布流程与规则 +## Release Process and Rules - Feature Development: Main branch development, branch releases, block user issues, critical bugs, security vulnerabilities, and high-priority fixes. It is given higher priority over general feature development and should be completed within a week. Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months.