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 51bb241 Updated RocketMQ Improvement Proposal (markdown)
51bb241 is described below
commit 51bb241e0f2628abed286140afd5ead1c1a47f07
Author: Heng Du <[email protected]>
AuthorDate: Wed Jan 9 16:21:37 2019 +0800
Updated RocketMQ Improvement Proposal (markdown)
---
RocketMQ-Improvement-Proposal.md | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/RocketMQ-Improvement-Proposal.md b/RocketMQ-Improvement-Proposal.md
index 08a413d..bd01968 100644
--- a/RocketMQ-Improvement-Proposal.md
+++ b/RocketMQ-Improvement-Proposal.md
@@ -2,4 +2,13 @@ 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]().
\ No newline at end of file
+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)
+* RIP 2 [RocketMQ
Spring](https://github.com/apache/rocketmq/wiki/RIP-2-RocketMQ-Spring)
+* RIP 3 [RocketMQ Python
Client](https://github.com/apache/rocketmq/wiki/RIP-3-RocketMQ-Python-Client)
+* 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)
+
