I find that when I upgrade RabbitMQ from one version to the next and the JS has changed in the management plugin, browser caches prevent the new JS from being loaded. In upgrading from 3.8.2 to 3.8.5 the following is what a user sees before clearing their cache:
A better user experience would be to use cache-busting query arguments or version specific filenames. This would allow rolling upgrades without the user having to take additional steps to get the UI to work properly in their browser.
This will be addressed with a new version of the UI. erlang.mk does not really offer any asset processing capabilities and any major changes to the UI side are hard to justify.
I find that when I upgrade RabbitMQ from one version to the next and the JS has changed in the management plugin, browser caches prevent the new JS from being loaded. In upgrading from 3.8.2 to 3.8.5 the following is what a user sees before clearing their cache:
A better user experience would be to use cache-busting query arguments or version specific filenames. This would allow rolling upgrades without the user having to take additional steps to get the UI to work properly in their browser.