Merge remote-tracking branch 'apache/develop' into 5.0.0-alpha

# Conflicts:
#	acl/pom.xml
#	broker/pom.xml
#	client/pom.xml
#	common/pom.xml
#	common/src/main/java/org/apache/rocketmq/common/MQVersion.java
#	distribution/pom.xml
#	example/pom.xml
#	filter/pom.xml
#	logging/pom.xml
#	namesrv/pom.xml
#	openmessaging/pom.xml
#	pom.xml
#	remoting/pom.xml
#	srvutil/pom.xml
#	store/pom.xml
#	store/src/test/java/org/apache/rocketmq/store/dledger/DLedgerCommitlogTest.java
#	test/pom.xml
#	tools/pom.xml

.github/ISSUE_TEMPLATE/issue_template.md

@@ -4,25 +4,36 @@ about: Describe this issue template's purpose here.
 
 ---
 
-The issue tracker is **ONLY** used for bug report(feature request need to follow [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal)). Keep in mind, please check whether there is an existing same report before your raise a new one.
+The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
 
-Alternately (especially if your communication is not a bug report), you can send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
+It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
+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:
+Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
+
+Generally, fixing an issue goes through the following steps:
+1. Understand the issue reported;
+1. Reproduce the unexpected behavior locally;
+1. Perform root cause analysis to identify the underlying problem;
+1. Create test cases to cover the identified problem;
+1. Work out a solution to rectify the behavior and make the newly created test cases pass;
+1. Make a pull request and go through peer review;
+
+As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
 
 **BUG REPORT**
 
 1. Please describe the issue you observed:
 
 - What did you do (The steps to reproduce)?
 
-- What did you expect to see?
+- What is expected 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):
+3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
 
 **FEATURE REQUEST**
 
@@ -32,7 +43,7 @@ Please ensure that your bug report is clear and that it is complete. Otherwise,
 
 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:
+4. If there are some sub-tasks involved, use -[] for each sub-task 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,

README.md

@@ -45,6 +45,8 @@ It offers a variety of features:
 * [RocketMQ Exporter](https://github.com/apache/rocketmq-exporter)
 * [RocketMQ Operator](https://github.com/apache/rocketmq-operator)
 * [RocketMQ Docker](https://github.com/apache/rocketmq-docker)
+* [RocketMQ Dashboard](https://github.com/apache/rocketmq-dashboard)
+* [RocketMQ Connect](https://github.com/apache/rocketmq-connect)
 * [RocketMQ Incubating Community Projects](https://github.com/apache/rocketmq-externals)
 
 ----------

acl/src/main/java/org/apache/rocketmq/acl/plain/PlainAccessValidator.java

@@ -163,15 +163,6 @@ public boolean deleteAccessConfig(String accesskey) {
         return aclPlugEngine.getAllAclConfig();
     }
 
-    public Map<String, Object> createAclAccessConfigMap(Map<String, Object> existedAccountMap,
-        PlainAccessConfig plainAccessConfig) {
-        return aclPlugEngine.createAclAccessConfigMap(existedAccountMap, plainAccessConfig);
-    }
-
-    public Map<String, Object> updateAclConfigFileVersion(Map<String, Object> updateAclConfigMap) {
-        return aclPlugEngine.updateAclConfigFileVersion(updateAclConfigMap);
-    }
-
     @Override
     public Map<String, DataVersion> getAllAclConfigVersion() {
         return aclPlugEngine.getDataVersionMap();