Shorter 4.1.1 release notes

(cherry picked from commit 1a4f0ff)

Author: michaelklishin

release-notes/4.1.1.md

@@ -1,19 +1,12 @@
-## RabbitMQ 4.1.1
-
 RabbitMQ `4.1.1` is a maintenance release in the `4.1.x` [release series](https://www.rabbitmq.com/release-information).
 
-Starting June 1st, 2024, community support for this series will only be provided to [regularly contributing users](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md) and those
-who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss).
-
 It is **strongly recommended** that you read [4.1.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0)
 in detail if upgrading from a version prior to `4.1.0`.
 
 
 ### Minimum Supported Erlang Version
 
-This release requires Erlang 26 and supports Erlang versions up to `27.3.x`.
-[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/docs/which-erlang) has more details on
-Erlang version requirements for RabbitMQ.
+[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/docs/which-erlang) has more details on Erlang version requirements for RabbitMQ.
 
 Nodes **will fail to start** on older Erlang releases.
 
@@ -37,14 +30,8 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
 
  * Empty classic queues init faster after a clean shutdown.
 
-   Contributed by @gomoripeti.
-
    GitHub issue: [#13870](https://github.com/rabbitmq/rabbitmq-server/pull/13870)
 
- * Private key password could appear in certain exceptions at (failed) node boot time.
-
-   GitHub issue: [#13999](https://github.com/rabbitmq/rabbitmq-server/pull/13999), [#14028](https://github.com/rabbitmq/rabbitmq-server/pull/14028)
-
 
 #### Bug Fixes
 
@@ -70,10 +57,22 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
  * RabbitMQ could fail to log certain client connection errors for TLS-enabled
    listeners.
 
-   Contributed by @LoisSotoLopez.
-
    GitHub issue: [#13985](https://github.com/rabbitmq/rabbitmq-server/pull/13985)
 
+ * Private key password could appear in certain exceptions at (failed) node boot time.
+
+   GitHub issue: [#13999](https://github.com/rabbitmq/rabbitmq-server/pull/13999), [#14028](https://github.com/rabbitmq/rabbitmq-server/pull/14028)
+
+
+### MQTT Plugin
+
+#### Bug Fixes
+
+ * When an MQTTv5 client that had a QoS 0 subscription is closed, the
+   transient queue that was backing it will now be deleted.
+
+   GitHub issue: [#14006](https://github.com/rabbitmq/rabbitmq-server/pull/14006)
+
 
 ### Stream Plugin
 
@@ -98,8 +97,6 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
    is a new command that forces a group of quorum queues to take a checkpoint and
    delete its on disk segment files, where possible.
 
-   Contributed by @aaron-seo.
-
    GitHub issue: [#13938](https://github.com/rabbitmq/rabbitmq-server/pull/13938)
 
 
@@ -110,43 +107,31 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
  * A separate chain for authentication and authorization backends now can be used
    used exclusively for the HTTP API and the management UI.
 
-   Contributed by @aaron-seo.
-
    GitHub issue: [#13819](https://github.com/rabbitmq/rabbitmq-server/pull/13819)
 
  * Reduced memory footprint of the plugin for certain workloads.
 
-   Contributed by @the-mikedavis.
-
    GitHub issue: [#13900](https://github.com/rabbitmq/rabbitmq-server/pull/13900)
 
  * When UI session expires, the user is redirected to the login page.
 
-   Contributed by @the-mikedavis.
-
    GitHub issue: [#13975](https://github.com/rabbitmq/rabbitmq-server/pull/13975)
 
  * `GET /api/health/checks/ready-to-serve-clients` is a new health check
    that responds a 200 OK if the target node has fewer connections to the AMQP
    and AMQPS ports than the configured maximum.
 
-   Contributed by @the-mikedavis.
-
    GitHub issue: [#13782](https://github.com/rabbitmq/rabbitmq-server/issues/13782)
 
  * `GET /api/health/checks/ready-to-serve-clients` is a new health check
    that responds a 200 OK if the target node is ready to serve clients
    (booted, not above the connection limit, not in [maintenance mode](https://www.rabbitmq.com/docs/upgrade#maintenance-mode)).
 
-   Contributed by @the-mikedavis.
-
    GitHub issue: [#13782](https://github.com/rabbitmq/rabbitmq-server/issues/13782)
 
  * Protocol listener health check now supports comma-separated lists of
    protocol names.
 
-   Contributed by @the-mikedavis.
-
    GitHub issue: [#13874](https://github.com/rabbitmq/rabbitmq-server/pull/13874)
 
  * New page for declaring super streams (partitioned streams).
@@ -173,7 +158,6 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
    GitHub issue: [#13801](https://github.com/rabbitmq/rabbitmq-server/pull/13801)
 
 
-
 ### Dependency Changes
 
  * `ra` was updated to [`2.16.9`](https://github.com/rabbitmq/ra/releases)