root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 9 Packages Projects Releases Wiki Activity

4.0.1 release notes: remove a pre-GA leftover

This commit is contained in:
Michael Klishin 2025-04-27 16:53:10 -04:00
parent 812d51be56
commit 005bb2c790
No known key found for this signature in database
GPG Key ID: 16AB14D00D613900
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
release-notes/4.0.1.md
View File

@ -218,7 +218,7 @@ Such clusters should be [migrated using the Blue/Green deployment strategy](http
RabbitMQ 4.0.0 nodes can run alongside `3.13.x` nodes. `4.0.x`-specific features can only be made available when all nodes in the cluster RabbitMQ 4.0.0 nodes can run alongside `3.13.x` nodes. `4.0.x`-specific features can only be made available when all nodes in the cluster
upgrade to 4.0.0 or a later patch release in the new series. upgrade to 4.0.0 or a later patch release in the new series.
While operating in mixed version mode, some aspects of the system may not behave as expected. The list of known behavior changes will be covered in future updates. While operating in mixed version mode, some aspects of the system may not behave as expected.
Once all nodes are upgraded to 4.0.0, these irregularities will go away. Once all nodes are upgraded to 4.0.0, these irregularities will go away.
Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended

2
release-notes/4.1.0.md
View File

@ -117,7 +117,7 @@ None. The required feature flag set is the same as in `4.0.x`.
RabbitMQ 4.1.0 nodes can run alongside `4.0.x` nodes. `4.1.x`-specific features can only be made available when all nodes in the cluster RabbitMQ 4.1.0 nodes can run alongside `4.0.x` nodes. `4.1.x`-specific features can only be made available when all nodes in the cluster
upgrade to 4.1.0 or a later patch release in the new series. upgrade to 4.1.0 or a later patch release in the new series.
While operating in mixed version mode, some aspects of the system may not behave as expected. The list of known behavior changes will be covered in future updates. While operating in mixed version mode, some aspects of the system may not behave as expected.
Once all nodes are upgraded to 4.1.0, these irregularities will go away. Once all nodes are upgraded to 4.1.0, these irregularities will go away.
Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended