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 ec109d1 Updated RIP (markdown)
ec109d1 is described below
commit ec109d14561a5d1e2e75cc7dd7639dc29f92c1aa
Author: von gosling <[email protected]>
AuthorDate: Wed Jan 9 16:20:43 2019 +0800
Updated RIP (markdown)
---
RIP.md | 1 -
RocketMQ-Improvement-Proposal.md | 5 +++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/RIP.md b/RIP.md
deleted file mode 100644
index 2579c2d..0000000
--- a/RIP.md
+++ /dev/null
@@ -1 +0,0 @@
-RocketMQ Improvement Proposals
diff --git a/RocketMQ-Improvement-Proposal.md b/RocketMQ-Improvement-Proposal.md
new file mode 100644
index 0000000..d0daa7f
--- /dev/null
+++ b/RocketMQ-Improvement-Proposal.md
@@ -0,0 +1,5 @@
+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.
+
+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
