This is an automated email from the ASF dual-hosted git repository.
yiguolei pushed a commit to branch branch-2.1
in repository https://gitbox.apache.org/repos/asf/doris.git
commit 5ed3c7eeef8236919179589d82692826865856f6
Author: Mingyu Chen <morning...@163.com>
AuthorDate: Tue Mar 5 12:38:55 2024 +0800
[opt](doc) update release verify (#31773)
---
docs/en/community/release-and-verify/release-verify.md | 4 +++-
docs/zh-CN/community/release-and-verify/release-verify.md | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/en/community/release-and-verify/release-verify.md
b/docs/en/community/release-and-verify/release-verify.md
index 92abf71d174..800912e8700 100644
--- a/docs/en/community/release-and-verify/release-verify.md
+++ b/docs/en/community/release-and-verify/release-verify.md
@@ -108,6 +108,8 @@ After the verification is completed, the following template
can be used to send
```
+1 (binding) or +1 (non-binding)
+My Apache ID(optional): morningman
+
I checked:
[x] The download link is legal.
@@ -123,7 +125,7 @@ Other comments...
For a release vote to pass, a minimum of three positive binding votes and more
positive binding votes than negative binding votes must be cast. Releases may
not be vetoed. Votes cast by PMC members are binding, however, non-binding
votes are greatly encouraged and a sign of a healthy project.
-Votes on whether a package is ready to release use majority approval -- at
least three PMC members must vote affirmatively for release, and there must be
more positive than negative votes. Releases may not be vetoed. For the sake of
easy auditing, PMC member votes are typically marked "binding." However, the
Release Manager needs to verify the validity of the votes. This can be done by
checking whether the email addresses on the PMC roster match the email
addresses of the voters.
+Votes on whether a package is ready to release use majority approval -- at
least three PMC members must vote affirmatively for release, and there must be
more positive than negative votes. Releases may not be vetoed. For the sake of
easy auditing, PMC member votes are typically marked "binding." However, the
Release Manager needs to verify the validity of the votes. This can be done by
checking whether the email addresses on the PMC roster match the email
addresses of the voters. Therefo [...]
Generally the community will cancel the release vote if anyone identifies
serious problems, but in most cases the ultimate decision lies with the
individual serving as release manager. The specifics of the process may vary
from project to project, but the 'minimum quorum of three +1 votes' rule is
universal.
diff --git a/docs/zh-CN/community/release-and-verify/release-verify.md
b/docs/zh-CN/community/release-and-verify/release-verify.md
index b108da9d174..5bfaf6326a2 100644
--- a/docs/zh-CN/community/release-and-verify/release-verify.md
+++ b/docs/zh-CN/community/release-and-verify/release-verify.md
@@ -112,6 +112,8 @@ INFO Totally checked 5611 files, valid: 3926, invalid: 0,
ignored: 1685, fixed:
```
+1 (binding) or +1 (non-binding)
+My Apache ID(optional): morningman
+
I checked:
[x] The download link is legal.
@@ -127,7 +129,7 @@ Other comments...
PMC 成员拥有具有约束力的投票，但一般来说，社区鼓励所有成员投票，即使他们的投票只是建议性的。
版本发布投票采用多数批准——即至少三名 PMC 成员必须对发布投赞成票，并且赞成票必须多于反对票。PMC
成员的投票是有约束力的，而其他投票则不是。但为了审查方便，PMC 成员投票通常显示指定 “binding”。
-但 Release Manager 需要检查投票的有效性。这可以通过 PMC 的花名册来验证电子邮件地址是否一致。
+但 Release Manager 需要检查投票的有效性。这可以通过 PMC 的花名册来验证电子邮件地址是否一致。所以，建议使用 Apache
邮箱进行投票，来确保投票的有效性。同时，也建议在投票中注明 Apache ID，方便 Release Manager 统计。
一般来说，如果有人发现严重问题，社区将取消发布投票，但在大多数情况下，最终决定权在于 Release
Manager。该流程的具体情况可能因项目而异，但“三+1 票的最低法定人数”规则是通用的。
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
