FEATURE REQUEST

1. Please describe the feature you are requesting.
   Add RocketMQ Dashboard 1.0.0 release note

2. Provide any additional detail on your proposed use case for this feature.
   Add RocketMQ Dashboard 1.0.0 release note

3. 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?
   must-have

4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
   NONE

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

Now we have a new website, but its links don't work with the old website. So old site links on search engines will cause 404. We can google for site: rocketmq.apache.org to verify it, only the home page is accessible in the top results.

I propose to maintain compatibility with old site links to optimize SEO. There are two ways to do this:

1. make the new website links as same as the old one
2. set 301 redirects to route traffic from an old path to a new URL

Moreover, URLs on the new website look weird. Maybe better to use slug.

https://rocketmq.apache.org/docs/%E4%BB%8B%E7%BB%8D/03whatis
-> https://rocketmq.apache.org/docs/what-is-rocketmq

To add the reference to the complete committee information of Apache RocketMQ in team document.

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

Polish release manual document

3. Provide any additional detail on your proposed use case for this feature.

4. 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?

5. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

Add auto switch deploy document

3. Provide any additional detail on your proposed use case for this feature.

4. 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?

5. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

2. Please tell us about your environment:

env: new official website

3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

FEATURE REQUEST

1. Please describe the feature you are requesting.

This issue init the rocketmq 5.0 doc, contains:

• concept.
• models.
• fetures.

3. Provide any additional detail on your proposed use case for this feature.

4. 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?

5. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

In order to make it easier for developers to understand the transactional component, a short design document I think is necessary.

一、
首页：https://rocketmq.netlify.app/
1.官网Banner条 在下滑至第二屏、第三屏时，需要吸顶常驻。（目前是直接跟随第一屏划走）
2.首页建议整体重新设计，按照「首屏简介（已有）」-「整体架构」-「特性一览」-「最新事件」-「用户案例（已有）」的排列进行重排。

二、
博客-用户案例/新闻/活动：https://rocketmq.netlify.app/blog
1.目前很多内容缺少内容，没有标题。是否有相关cms后台，可以直接由相关管理员或维护者直接上传相关内容。
2.新增一个专门展示页面，展现项目的服务企业logo墙
3.过往线上直播相关内容缺乏相关的展示页面

三、
社区-加入我们：https://rocketmq.netlify.app/contact
1.公众号二维码已过期，需更新
2.关注博客action，没有订阅功能，只是站内跳转，建议删除这个模块。

四、
全站Title 、description、keyword需要针对性修改，目前跟页面内容对应不上。

五、
其他：
目前对于SIG、上下游合作生态的相关内容缺乏展示

add GitHub actions to build new official website

format new web site code:

• remove useless file
• fix travis ci
• update docusaurus version to stable release

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

Fix 16dledger.md file some Using Command Problems

2. Please tell us about your environment:

env: new-official-website-develop
rocketmqversion: 5.0

3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

Consider we have migrated from Jira to issues[1]. this mail list has lost its value. Anybody would like to remove it ?

[1] https://rocketmq.apache.org/about/contact/

I just pulled apache/rocketmq-site to the local by mistake, and directly pushed the code to the master branch. Is it possible to control the authority of the master to avoid pushing directly to the master?

Details

1. Add preserving properties information.
2. Add transaction check timeout information.

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

FEATURE REQUEST

1. Add rocketmq 5.0 en doc for quickstart,concepts,models,features

2. The deployment guidelines, best practices, and other chapters will need to be translated in the future

please review

Request to release rocketmq cpp client 1.2.5

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

Commands are not well differentiated in the table, as following picture:

2. Please tell us about your environment:

new official webstie

3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

1. Please describe the issue you observed:

• What did you do (The steps to reproduce)?
  npm run build

• What did you expect to see?
  build success

• What did you see instead?

    Unable to build website for locale "zh".
    Error: Docusaurus found broken links!

    Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
    Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

seems path link error.

It looks like some of the broken links we found appear in many pages of your site.
Maybe those broken links appear on all pages through your site layout?
We recommend that you check your theme configuration for such links (particularly, theme navbar and footer).
Frequent broken links are linking to:
- /changelog


Exhaustive list of all broken links found:

- On source page path = /404.html:
   -> linking to /changelog

- On source page path = /:
   -> linking to /changelog

- On source page path = /blog:
   -> linking to /changelog

- On source page path = /blog/01xiaohongshu:
   -> linking to /changelog

- On source page path = /blog/archive:
   -> linking to /changelog

2. Please tell us about your environment:
   • macOS Big Sur 11.5.1
   • [email protected]
   • [email protected]
   • [email protected]
3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

In Class OrderedProducer I find some typo.

 Message msg = new Message("TopicTestjjj", tags[i % tags.length], "KEY" + i,

TopicTestjjj should be TopicTest

Add quick start guide for windows user

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

• What did you do (The steps to reproduce)?
  Polish release manual again

• What did you expect to see?

Polish release manual again

• 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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

URL:https://rocketmq.apache.org/docs/%E7%94%9F%E4%BA%A7%E8%80%85/04concept1 page Note display problem

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

https://rocketmq.apache.org/docs/motivation/

RocketMQ vs. ActiveMQ vs. Kafka

High Availability and Failover:

Supported, depending on storage,if using kahadb it requires a ZooKeeper server.

or levelDB?

http://activemq.apache.org/persistence

In ActiveMQ 5.9, the Replicated LevelDB Store is introduced. It handles using Apache ZooKeeper to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates to the master. This might become the preferred Master Slave configuration going forward.

• 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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

• What did you do (The steps to reproduce)?

In https://github.com/apache/rocketmq-site/blob/new-official-website/versioned_docs/version-5.0/04-%E5%8A%9F%E8%83%BD%E8%A1%8C%E4%B8%BA/01normalmessage.md

There are several classes in the demo of ordinary messages that are not found in the 5.0 source code

e.g.
MessageBuilder
SendReceipt

Is the source code released now incomplete?

• 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):

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

Any question or RocketMQ proposal please use our mailing lists.

FEATURE REQUEST

1. What did you do (The steps to reproduce)?

   • Add 17Dashboard.md to rocketmq-site\docs\04-部署与运维\

   • Add 17Dashboard to rocketmq-site\docs\picture

2. Please tell us about your environment:

   • centos 7 local virtual machine
   • centos 7 aliyun remote virtual machine
   • maven 3.8.5 jdk 1.8
   • rocketmq 4.9.3, 4.9.4
   • rocketmq dashboard 1.0.0

3. Please describe the feature you are requesting.

   • add introduction about the rocketmq dashboard
   • add install guide and uer guide

增加 rocketmq-site 仓库链接（https://github.com/apache/rocketmq-site）以及说明到readme

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

Add multiple language support.

npm run buils error:

Error: Image i18n/en/docusaurus-plugin-content-docs/current/01-介绍/docs/picture/RocketMQ概念模型.png used in i18n/en/docusaurus-plugin-content-docs/current/01-介绍/03whatis.md not found.
    at async Promise.all (index 0)
Error: Image i18n/en/docusaurus-plugin-content-docs/current/02-生产者/docs/picture/同步发送.png used in i18n/en/docusaurus-plugin-content-docs/current/02-生产者/05message1.md not found.
    at async Promise.all (index 0)
Error: Image i18n/en/docusaurus-plugin-content-docs/current/02-生产者/docs/picture/顺序消息发送.png used in i18n/en/docusaurus-plugin-content-docs/current/02-生产者/06message2.md not found.
    at async Promise.all (index 0)
Error: Image i18n/en/docusaurus-plugin-content-docs/current/02-生产者/docs/picture/batch.png used in i18n/en/docusaurus-plugin-content-docs/current/02-生产者/08message4.md not found.
    at async Promise.all (index 0)
Error: Image i18n/en/docusaurus-plugin-content-docs/current/02-生产者/docs/picture/事务消息1.png used in i18n/en/docusaurus-plugin-content-docs/current/02-生产者/09message5.md not found.
    at async Promise.all (index 0)

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

1. Please describe the issue you observed:

• What did you do (The steps to reproduce)?

i see the quick_start for windows is only for the binary release. For the source code build, the environment variable setting is different for win10 . So i add these and add the develop guide for lauch nameserver、broker、producer 、 consumer on the idea。
this is for homework :)

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

Now we have a new website, but its links don't work with the old website. So old site links on search engines will cause 404. We can google for site:rocketmq.apache.org to verify it, only the home page is accessible in the top results.

I propose to maintain compatibility with old site links to optimize SEO. There are two ways to do this:

1. make the new website links as same as the old one
2. set 301 redirects to route traffic from an old path to a new URL

Moreover, URLs on the new website look weird. Maybe better to use slug.

https://rocketmq.apache.org/docs/%E4%BB%8B%E7%BB%8D/03whatis
-> https://rocketmq.apache.org/docs/what-is-rocketmq

FEATURE REQUEST
RIP list has been moved to RocketMQ WIKI, so the information of the website needs to be updated.

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

FEATURE REQUEST

1. merge new-official-website to new-official-website-develop
2. merge rocketmq 5.0 doc and en doc #251
3. fix build error

add new member to the contributor list

FEATURE REQUEST

Since the 4.3.0 version is about to be released, a release note should be added to the site.

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

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):

FEATURE REQUEST

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

3. 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: sub-task1 description here,
• sub-task2-issue-number: sub-task2 description here,
• ...

In order to facilitate the use of the transactional message, I think we should add the example of transactional message.