From 7e267e17e2da4e2e64e4838150138691f0d23bb2 Mon Sep 17 00:00:00 2001
From: Michael Klishin <klishinm@vmware.com>
Date: Fri, 8 Sep 2023 10:39:28 -0400
Subject: [PATCH] 3.11.23 release notes

---
 release-notes/3.11.23.md | 70 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 release-notes/3.11.23.md

diff --git a/release-notes/3.11.23.md b/release-notes/3.11.23.md
new file mode 100644
index 000000000000..42a95c4fa735
--- /dev/null
+++ b/release-notes/3.11.23.md
@@ -0,0 +1,70 @@
+RabbitMQ `3.11.23` is a maintenance release in the `3.11.x` [release series](https://www.rabbitmq.com/versions.html).
+This release series [goes out of community support on Dec 31, 2023](https://rabbitmq.com/versions.html).
+
+Please refer to the upgrade section from [v3.11.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.11.0)
+if upgrading from a version prior to 3.11.0.
+
+This release requires Erlang 25 and supports Erlang versions up to `25.3.x`.
+[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/which-erlang.html) has more details on
+Erlang version requirements for RabbitMQ.
+
+
+### Minimum Supported Erlang Version
+
+As of 3.11.0, RabbitMQ requires Erlang 25. Nodes **will fail to start** on older Erlang releases.
+
+Erlang 25 as our new baseline means much improved performance on ARM64 architectures, [profiling with flame graphs](https://blog.rabbitmq.com/posts/2022/05/flame-graphs/)
+across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users.
+
+
+## Changes Worth Mentioning
+
+Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.11.x/release-notes).
+
+
+### Core Server
+
+#### Bug Fixes
+
+ * High consumer churn with reused consumer tag on quorum queues could result in some messages not being delivered
+   after a period of time.
+
+   This did not affect environments where consumer churn does not exist or where it does but consumer tags vary.
+
+   GitHub issue: [#9164](https://github.com/rabbitmq/rabbitmq-server/pull/9164)
+
+ * Three environment variables, `LOG_BASE`, `MNESIA_BASE`, `CONFIG_FILE`, were not picked up when set in
+   `rabbitmq-env-conf.bat` on Windows.
+
+   GitHub issue: [#9308](https://github.com/rabbitmq/rabbitmq-server/pull/9308)
+
+ * Avoids a potential exception when autoheal partition handling process was initiated.
+
+   GitHub issue: [#9223](https://github.com/rabbitmq/rabbitmq-server/pull/9223)
+
+
+### AMQP 1.0 Plugin
+
+#### Bug Fixes
+
+* Reverted [#8739](https://github.com/rabbitmq/rabbitmq-server/pull/8739) where unroutable AMQP 1.0 messages were settled with
+  a "released" disposition state. Some clients do not handle this outcome correctly, throwing exceptions,
+  which can create unnecessary and resource-consuming client reconnection and re-publishing loops.
+
+  On the RabbitMQ node end this looks like abnormally high CPU usage of a node that takes in a certain number of unroutable messages.
+
+  The original change (#8739) will be re-introduced with options for better compatibility with such irregularly-behaved clients
+  in RabbitMQ 3.13.x or 3.12.x.
+
+  GitHub issue: [#9334](https://github.com/rabbitmq/rabbitmq-server/pull/9334)
+
+
+## Dependency Upgrades
+
+ * `osiris` was upgraded to [`1.6.4`](https://github.com/rabbitmq/osiris/tags)
+
+
+## Source Code Archives
+
+To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.23.tar.xz`
+instead of the source tarball produced by GitHub.