The release notes do a great job of calling out any breaking changes
in terms of gateway format or config files:
However, it'd be great if any updates that impact the compatibility of
Java API protocols were called out, as well.
For example, I am on master from last week and am moving up to the
current master and the only way to know if the Java APIs are still
compatible is to just give it a shot. My preference is to perform a
rolling update, but if I knew there was an incompatibility would have
to bring down the whole cluster and upgrade it all at the same time.
Along these same lines and probably a better approach, it'd be best if
the APIs detected you were attempting to talk to an incompatible
version and log out the failure and refuse to join.