Hello, While doing code-reviews there are times that I observe changes (let's assume that they are meaningful and inevitable) to public classes/methods/fields that could break clients if they are relying on them. In some cases, the changes may occur in some internal APIs that it is rather unlikely to be used by clients; still the classes are public and accessible. I was thinking that even then it is worth adding a few words in the release note but maybe I am going too far.
I was wondering if there is a common agreement on this topic. Best, Stamatis
