Skip to content

Commit b1796ef

Browse files
committed
chore: format all documents
Signed-off-by: peefy <xpf6677@163.com>
1 parent 1ec4494 commit b1796ef

File tree

44 files changed

+432
-612
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+432
-612
lines changed

docs/community/contribute/git-guideline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ The branch name mainly includes two fields, which are separated by "-". Includin
3232

3333
For example, Alice first transfers the Fork warehouse to his own account, and then creates a branch with the corresponding name 'alice: fix output fmt bug' (Alice's account is before the colon) to fix the output formatting bug.
3434

35-
## 3. 关于 Git Commit
35+
## 3. About Git Commit
3636

3737
We refer to [Commitizen](https://github.com/commitizen/cz-cli) to write a Commit Message.
3838

docs/community/release-policy/kcl.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The KCL project version release strategy is as follows:
1414
## Release Process and Rules
1515

1616
- 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.
17-
Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months.
17+
- Iteration Cycle: The iteration cycle is typically 3 months, with a new minor version released every 3 months.
1818
- Version Planning: Two weeks before the release, an alpha version is produced, followed by a beta version one week before the release. Alpha versions can still include feature merging, while beta versions only include bug fixes. The final release version is tagged as a long-term saved release branch.
1919
- Release Plan: A detailed release plan (Github Milestone) is created at the beginning of each release cycle, including release dates, version numbers, feature lists, and testing plans. The release plan should be followed as closely as possible to ensure timely releases.
2020
- Pre-release Testing: Comprehensive testing, including unit testing, integration testing, fuzz testing, stress testing, and user acceptance testing, is conducted before releasing a new version. The new version is only released when it passes all tests without any issues.

0 commit comments

Comments
 (0)