calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stamatis Zampetakis <>
Subject Breaking changes and internal APIs
Date Tue, 07 May 2019 13:17:01 GMT

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
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
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.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message