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 ec16b07 Updated RocketMQ Improvement Proposal (markdown)
ec16b07 is described below
commit ec16b07618cfb59fee17645008c446b57bafcdde
Author: Heng Du <[email protected]>
AuthorDate: Wed Jan 9 16:24:09 2019 +0800
Updated RocketMQ Improvement Proposal (markdown)
---
RocketMQ-Improvement-Proposal.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/RocketMQ-Improvement-Proposal.md b/RocketMQ-Improvement-Proposal.md
index 3481941..28fc205 100644
--- a/RocketMQ-Improvement-Proposal.md
+++ b/RocketMQ-Improvement-Proposal.md
@@ -3,7 +3,6 @@ In the last few years, we use the
[Jira](https://issues.apache.org/jira/projects
RIPs should be used for significant user-facing or cross-cutting changes, not
small incremental improvements. When in doubt, if a committer thinks a change
needs an RIP, it does.
It is easy to start a RIP from sending proposals to dev mail lists. And the
whole procedure of a RIP may follow below [RIP Template]().
-# RocketMQ Improvement Proposals
## EN
* RIP 1 [RocketMQ MQTT
Bridge](https://github.com/apache/rocketmq/wiki/RIP-1-MQTT-Bridge)
@@ -12,3 +11,5 @@ It is easy to start a RIP from sending proposals to dev mail
lists. And the whol
* RIP 4 [RocketMQ Go
Client](https://github.com/apache/rocketmq/wiki/RIP-4-RocketMQ-Go-Client)
* RIP 5 [RocketMQ Message
Track](https://github.com/apache/rocketmq/wiki/RIP-5-Message-Track-Trace)
+## CN
+* RIP 6 [RocketMQ
ACL](https://github.com/apache/rocketmq/wiki/RIP-6-RocketMQ-ACL)
