This is an automated email from the ASF dual-hosted git repository.
vongosling 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 3240224 Updated RocketMQ Improvement Proposal (markdown)
3240224 is described below
commit 3240224326cfeea60af1238dce0c1c995b371b64
Author: von gosling <[email protected]>
AuthorDate: Wed Jan 9 16:20:56 2019 +0800
Updated RocketMQ Improvement Proposal (markdown)
---
RocketMQ-Improvement-Proposal.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/RocketMQ-Improvement-Proposal.md b/RocketMQ-Improvement-Proposal.md
index d0daa7f..08a413d 100644
--- a/RocketMQ-Improvement-Proposal.md
+++ b/RocketMQ-Improvement-Proposal.md
@@ -2,4 +2,4 @@ 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]().
\ No newline at end of file
