This is an automated email from the ASF dual-hosted git repository.

zhaojinchao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 1921a639a7c Update release document (#37697)
1921a639a7c is described below

commit 1921a639a7c79b8bedf70788701863bc74193807
Author: Raigor <[email protected]>
AuthorDate: Sat Jan 10 17:22:26 2026 +0800

    Update release document (#37697)
    
    * Update release document
    
    * Update release document
---
 docs/community/content/involved/release/shardingsphere.cn.md | 10 ++++++----
 docs/community/content/involved/release/shardingsphere.en.md | 10 ++++++----
 2 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/docs/community/content/involved/release/shardingsphere.cn.md 
b/docs/community/content/involved/release/shardingsphere.cn.md
index 6e98fb0f28f..16f6247794c 100644
--- a/docs/community/content/involved/release/shardingsphere.cn.md
+++ b/docs/community/content/involved/release/shardingsphere.cn.md
@@ -16,10 +16,12 @@ chapter = true
 
 ### 2. 确认 Release Note
 
-Release Note 需提供中文/英文两种版本,确认中英文描述是否明确,并按以下标签进行分类:
+确认 Release Note 中的内容完整,描述准确,并按以下标签进行分类:
 
-1. 新功能
+1. CVE
+1. 元数据存储变更
 1. API 变更
+1. 新功能
 1. 功能增强
 1. 漏洞修复
 
@@ -47,9 +49,9 @@ Release Note 需提供中文/英文两种版本,确认中英文描述是否明
 
 ### 6. 发起发布讨论
 
-1. 创建 [GitHub 
Discussion](https://github.com/apache/shardingsphere/discussions) 并在讨论内容中列出 
Release Note,并 **明确具体代码冻结日期** ;
+1. 创建 [GitHub Issue](https://github.com/apache/shardingsphere/issues),在 Issue 
内容中列出 Release Note,并 **明确具体代码冻结日期** ;
 1. 发送邮件至 
[[email protected]](mailto:[email protected]),在邮件正文中链接
 GitHub Discussion,并 **明确具体代码冻结日期** ;
-1. 关注 Discussion 与邮件列表,确认社区开发者对 Release Note 没有任何疑问。
+1. 关注 Issue 与邮件列表,确认社区开发者对 Release Note 没有任何疑问。
 
 ## GPG 设置
 
diff --git a/docs/community/content/involved/release/shardingsphere.en.md 
b/docs/community/content/involved/release/shardingsphere.en.md
index 999ee613881..184d532f2c1 100644
--- a/docs/community/content/involved/release/shardingsphere.en.md
+++ b/docs/community/content/involved/release/shardingsphere.en.md
@@ -16,9 +16,11 @@ Check and update year in NOTICE.
 
 ### 2. Confirm Release Notes
 
-The release note should be provided in English / Chinese, confirm whether 
English and Chinese description are clear,
-and shall be classified according to the following labels:
+Confirm that the content in the release note is complete and accurate, and 
categorize it according to the following labels:
 
+1. CVE
+1. Metadata Storage Changes
+1. API Change
 1. New Feature
 1. API Change
 1. Enhancement
@@ -48,9 +50,9 @@ Open [GitHub pull 
requests](https://github.com/apache/shardingsphere/pulls), fil
 
 ### 6. Call for a Discussion
 
-1. Create a [GitHub 
Discussion](https://github.com/apache/shardingsphere/discussions) contains all 
the release notes and **release cutting date** ;
+1. Create a [GitHub Issue](https://github.com/apache/shardingsphere/issues) 
contains all the release notes and **release cutting date** ;
 1. Send email to 
[[email protected]](mailto:[email protected]) with 
the GitHub Discussion and **release cutting date** in the message body;
-1. Follow the mailing list and confirm that the community developers have no 
questions about the release note.
+1. Follow the issue and mailing list and confirm that the community developers 
have no questions about the release note.
 
 ## GPG Settings
 

Reply via email to