rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [rocketmq-docker] 13/50: Update issue templates
Date Tue, 03 Dec 2019 13:50:36 GMT
This is an automated email from the ASF dual-hosted git repository.

vongosling pushed a commit to branch master
in repository

commit fa704fcbae908a9abb4822107dc57e2c0cc6f008
Author: von gosling <>
AuthorDate: Wed Jul 31 15:27:08 2019 +0800

    Update issue templates
 .github/ISSUE_TEMPLATE/ | 42 ++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/.github/ISSUE_TEMPLATE/ b/.github/ISSUE_TEMPLATE/
new file mode 100644
index 0000000..bbf88c2
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/
@@ -0,0 +1,42 @@
+about: Describe this issue template's purpose here.
+title: ''
+labels: ''
+assignees: ''
+The issue tracker is **ONLY** used for bug report(feature request need to follow [RIP process](
Keep in mind, please check whether there is an existing same report before your raise a new
+Alternately (especially if your communication is not a bug report), you can send mail to
our [mailing lists]( We welcome any friendly suggestions,
bug fixes, collaboration and other improvements.
+Please ensure that your bug report is clear and that it is complete. Otherwise, we may be
unable to understand it or to reproduce it, either of which would prevent us from fixing the
bug. We strongly recommend the report(bug report or feature request) could include some hints
as the following:
+1. Please describe the issue you observed:
+- What did you do (The steps to reproduce)?
+- What did you expect to see?
+- What did you see instead?
+2. Please tell us about your environment:
+3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to
fix, etc):
+1. Please describe the feature you are requesting.
+2. Provide any additional detail on your proposed use case for this feature.
+2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have).
Are you currently using any workarounds to address this issue?
+4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue
to map to the sub task:
+- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, 
+- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
+- ...

View raw message