Update 4.0.0 release notes

rabbitmq · Aug 13, 2024 · dbf498a · dbf498a
1 parent 5c61d73
commit dbf498a
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/release-notes/4.0.0.md b/release-notes/4.0.0.md
@@ -9,13 +9,13 @@ Starting June 1st, 2024, community support for this series will only be provided
 Some key improvements in this release are listed below.
 
  * [Khepri](https://www.youtube.com/watch?v=whVqpgvep90), an [alternative schema data store](https://github.com/rabbitmq/rabbitmq-server/pull/7206) developed to replace Mnesia, has matured
- * AMQP 1.0 is now a core protocol that is always enabled. Its plugin is now a no-op that only exists to simplify upgrades.
+ * [AMQP 1.0 is now a core protocol](https://www.rabbitmq.com/blog/2024/08/05/native-amqp) that is always enabled. Its plugin is now a no-op that only exists to simplify upgrades.
  * The AMQP 1.0 implementation is now significantly more efficient: its peak throughput is [more than double than that of 3.13.x](https://github.com/rabbitmq/rabbitmq-server/pull/9022)
    on some workloads
  * Efficient sub-linear [quorum queue recovery on node startup using checkpoints](https://github.com/rabbitmq/rabbitmq-server/pull/10637)
  * Quorum queues now [support priorities](https://github.com/rabbitmq/rabbitmq-server/pull/10637) (but not exactly the same way as classic queues)
  * [AMQP 1.0 clients now can manage topologies](https://github.com/rabbitmq/rabbitmq-server/pull/10559) similarly to how AMQP 0-9-1 clients do it
- * The AMQP 1.0 convention (address format) used for interacting with with AMQP 0-9-1 entities [is now easier to reason about](https://github.com/rabbitmq/rabbitmq-server/pull/11618)
+ * The AMQP 1.0 convention (address format) used for interacting with with AMQP 0-9-1 entities [is now easier to reason about](https://www.rabbitmq.com/docs/next/amqp#address)
  * Mirroring (replication) of classic queues [was removed](https://github.com/rabbitmq/rabbitmq-server/pull/9815) after several years of deprecation. For replicated messaging data types,
    use quorum queues and/or streams. Non-replicated classic queues remain and their development continues
  * Classic queue [storage efficiency improvements](https://github.com/rabbitmq/rabbitmq-server/pull/11112), in particular recovery time and storage of multi-MiB messages