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 45e4806 Updated RocketMQ Improvement Proposal (markdown)
45e4806 is described below
commit 45e4806086c4d5015ce8880a0f6dfbae2681e9e3
Author: von gosling <[email protected]>
AuthorDate: Wed Jan 9 16:23:05 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 bd01968..3481941 100644
--- a/RocketMQ-Improvement-Proposal.md
+++ b/RocketMQ-Improvement-Proposal.md
@@ -1,4 +1,4 @@
-In the last few years, we use the
[Jira](https://issues.apache.org/jira/projects/ROCKETMQ)(migrated to Issues) to
trace issue or collect new idea from the community. It’s a nice way for a
feature request but not very formal and easy to trace and manage. So We
introduce the RIP(RocketMQ Improvement Proposal) mechanism to replace the
current Feature Request Process.
+In the last few years, we use the
[Jira](https://issues.apache.org/jira/projects/ROCKETMQ)(migrated to Issues) to
trace issue or collect new idea from the community. It’s a nice way for a
feature request but not very formal and easy to trace and manage. So We
introduce the RIP - RocketMQ Improvement Proposal mechanism to replace the
current Feature Request Process.
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.
