v4.1.0

[michaelklishin]

Build Details

Built against RabbitMQ server 4.1.0 on Erlang/OTP 26.2.5.11.

Breaking Changes and Compatibility Notes

This plugin is 4.1.x compatible with the following limitations:

1. If the cluster uses Mnesia for schema store, it works exactly as it did against RabbitMQ 3.13.x
2. If the cluster uses Khepri and the plugin is enabled after Khepri, it will start Mnesia, set up a node-local Mnesia replica and schema, and works as in scenario 1
3. Important: if the cluster uses Mnesia, then the plugin is enabled, and then Khepri is enabled, the plugin must be disabled and re-enabled, or the node must be restarted. Then it will start Mnesia and works as in scenario 2

Changes

• RabbitMQ 4.1.0 compatibility.

---

This discussion was created from the release v4.1.0.

[michaelklishin]

I have removed a thread about the file naming changes (which happened in 4.0.7, this version does match 4.0.2), as well as people complaining about being "annoyed" by it, as well as a claim that "this plugin should be versionless".

RabbitMQ internals change, and increasingly rapidly so, so plugins have to be updated from time to time. For example, anything dependent on Mnesia (like this plugin) is almost guaranteed to need an update from time to time because Mnesia is on its way out.

So this plugin gets an update every major and minor, occasionally every N patch releases, as was the case with 4.0.7 where a completely reasonable change in the core broke this plugin because of certain decisions many years ago.

This Plugin Has Been on Life Support for a While

This plugin's README is very clear: it is no longer developed and we pretty much minimally
update it out of the core team's good will and the interest in getting the community off the 3.x
era.

This plugin has very serious limitations. It badly needs a different design and getting there takes a non-trivial investment: I'm speaking from experience. Due to the amount of effort
required, a new design will likely ship in a future version Tanzu RabbitMQ.

To Those "Annoyed" But Unwilling to Neither Contribute Nor Pay

Those who are "annoyed" by this can fork it and maintain it, automate the releases for their needs, invest time into implementing one of the design outlines in #229 #253, and so on.

Team RabbitMQ's focus is on core RabbitMQ, Tanzu RabbitMQ, client libraries, docs. We are a small team and we work with the resources we have, all while keeping RabbitMQ MPLv2-licensed.

Those who are annoyed by the status quo can take this code and run with it.