4.0.1 release notes: remove a pre-GA leftover
(cherry picked from commit 005bb2c790
)
This commit is contained in:
parent
7aaef695cd
commit
1f6964a333
|
@ -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
|
||||
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.
|
||||
|
||||
Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended
|
||||
|
|
|
@ -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
|
||||
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.
|
||||
|
||||
Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended
|
||||
|
|
Loading…
Reference in New Issue