This is an automated email from the ASF dual-hosted git repository.
duhengforever pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 0dd254b Updated RocketMQ Improvement Proposal (markdown)
0dd254b is described below
commit 0dd254b157107f8ef3bf8478cc77a4aa27e3c86e
Author: Heng Du <[email protected]>
AuthorDate: Wed Jan 9 19:07:40 2019 +0800
Updated RocketMQ Improvement Proposal (markdown)
---
RocketMQ-Improvement-Proposal.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/RocketMQ-Improvement-Proposal.md b/RocketMQ-Improvement-Proposal.md
index b80f3ba..32abc68 100644
--- a/RocketMQ-Improvement-Proposal.md
+++ b/RocketMQ-Improvement-Proposal.md
@@ -8,9 +8,9 @@ It is easy to start a RIP from sending proposals to dev mail
lists. And the whol
2. Start a [DISCUSS] thread on the Apache RocketMQ dev mailing list. Please
ensure that the subject of the thread is of the format [DISCUSS] RIP-{your RIP
number} {your RIP heading} The discussion should happen on the mailing list not
on the wiki since the wiki comment system doesn't work well for larger
discussions. In the process of the discussion, you may update the proposal. You
should let people know the changes you are making. When you feel you have a
finalized proposal.
-3. Once the proposal is finalized and some committers(Shepherd) are willing to
support, please call a [VOTE] to have the proposal adopted. These proposals are
more serious than code changes and more serious even than release votes. The
criteria for acceptance is lazy majority. The vote should remain open for 72
hours.
+3. Once the proposal is finalized and some committers(Shepherd) are willing to
support, please call a [VOTE] to have the proposal adopted. These proposals are
more serious than code changes and more serious even than release votes. The
criteria for acceptance is the lazy majority. The vote should remain open for
72 hours.
-4. Please update the RIP wiki page, and the index below, to reflect the
current stage of the RIP after a vote. This acts as the permanent record
indicating the result of the RIP (e.g., Accepted or Rejected). Also report the
result of the RIP vote to the voting thread on the mailing list so the
conclusion is clear.
+4. Please update the RIP wiki page, and the index below, to reflect the
current stage of the RIP after a vote. This acts as the permanent record
indicating the result of the RIP (e.g., Accepted or Rejected). Also, report the
result of the RIP vote to the voting thread on the mailing list so the
conclusion is clear.
### EN
* RIP-1 Accepted Inactive [RocketMQ MQTT
Bridge](https://github.com/apache/rocketmq/wiki/RIP-1-MQTT-Bridge)
@@ -18,6 +18,6 @@ It is easy to start a RIP from sending proposals to dev mail
lists. And the whol
* RIP-3 Accepted Release [RocketMQ Python
Client](https://github.com/apache/rocketmq/wiki/RIP-3-RocketMQ-Python-Client)
* RIP-4 Accepted Release [RocketMQ Go
Client](https://github.com/apache/rocketmq/wiki/RIP-4-RocketMQ-Go-Client)
* RIP-5 Accepted Release [RocketMQ Message
Trace](https://github.com/apache/rocketmq/wiki/RIP-6-Message-Track-Trace)
-* RIP-7 Discussing Inactive [Multiple Directories Storage
Support](https://github.com/apache/rocketmq/wiki/RIP-7-Multiple-Directories-Storage-Support)
+* RIP-7 Accepted Inactive [Multiple Directories Storage
Support](https://github.com/apache/rocketmq/wiki/RIP-7-Multiple-Directories-Storage-Support)
### CN
* RIP-6 Accepted [RocketMQ
ACL](https://github.com/apache/rocketmq/wiki/RIP-5-RocketMQ-ACL)
