Skip to main content

Announcing Changes to the Open Source RabbitMQ Release and Community Support Policy

· 2 min read

Effective June 1st, the RabbitMQ community support and release policies will change for the open source distributions of RabbitMQ. The goal of these changes is to ensure that the RabbitMQ team has time to focus on developing new features for the Open Source and commercial versions of RabbitMQ.

What is Community Support?

Community support is defined as all questions, root cause analysis requests, issue reports, and other interactions the RabbitMQ core team has with open source RabbitMQ users on GitHub and our community forums.

Community Support Policy Changes

Effective immediately, a new community support policy is adopted for Open Source distributions of RabbitMQ. The policy seeks to ensure that RabbitMQ remains a sustainable open source project.

Under the new policy, only the following groups of users will receive support directly from the RabbitMQ core team:

Release Policy Changes

Effective June 1st 2024, the RabbitMQ team will adopt a new release policy for the Open Source distribution. The changes do not impact the current RabbitMQ Open Source License. The RabbitMQ core team will continue developing Open Source RabbitMQ under the Mozilla Public License 2.0 on GitHub.

With the new policy, older Open Source release versions (for example, RabbitMQ 3.12.x and older) will no longer receive patches through community support. Patches for older versions of both the Open Source and Commercial versions will be available to customers that have VMware Tanzu RabbitMQ commercial licenses.

In practical terms this means that once RabbitMQ 4.x is released, all new contributions will eventually ship as part of

  • Open Source RabbitMQ 4.x
  • VMware Tanzu RabbitMQ 4.x


Users who contribute to the RabbitMQ open source distribution, and/or stay current with the latest RabbitMQ release will still have the ability to collaborate with the RabbitMQ team.

All other users seeking assistance with the RabbitMQ Open Source distribution will be required to obtain commercial licenses for RabbitMQ support or seek RabbitMQ-related help elsewhere.

Erlang/OTP 27 Is Currently Not Supported

· One min read

Erlang/OTP 27.0 was released on May 20th, 2024. While it contains a lot of exciting features and improvements, unfortunately RabbitMQ currently doesn't work well with this version. We are aware of significant performance regressions, as high as 30% lower message throughput in many common workloads.

We are investigating the root cause of this regression. Please do not use Erlang/OTP 27 with RabbitMQ at this time.

We will announce support for Erlang/OTP 27 when we are confident that it works well with RabbitMQ.

RabbitMQ 3.13.0 Is Here!

· 5 min read

RabbitMQ 3.13 is now available with support for MQTTv5, stream filtering and significant improvements to classic queue performance, especially for larger messages.

Read dedicated blog posts for more details about these changes:

RabbitMQ 3.13 is the final minor release in the 3.x series. The next release will be 4.0!

New website for RabbitMQ 3.13.0

· 5 min read

We have been working for several weeks on a new website for RabbitMQ. We plan to release this significant upgrade shortly after RabbitMQ 3.13.0 is released! At this point, we would love you to visit the new website and tell us what you think :-)

In this blog post, I will go over the reasons we are doing this and what improvements it will bring to you.

Screenshot of the new homepage Screenshot of the new homepage

Screenshot of the new homepage

RabbitMQ 3.12 Performance Improvements

· 13 min read

RabbitMQ 3.12 will be released soon with many new features and improvements. This blog post focuses on the the performance-related differences. The most important change is that the lazy mode for classic queues is now the standard behavior (more on this below). The new implementation should be even more memory efficient while proving higher throughput and lower latency than both lazy or non-lazy implementations did in earlier versions.

For even better performance, we highly recommend switching to classic queues version 2 (CQv2).