It may not manifest on the mailing list, but it does cause pain to Calcite developers. Every time we change or remove a public method we have to leave the old method marked deprecated until the next major release.
On Wed, Oct 14, 2015 at 11:56 AM, Vladimir Sitnikov <[email protected]> wrote: > I think we had a discussion on "public method" vs "published > interface" once (somewhere near 1.0 release). > For instance, adding an explicit annotation like @CalcitePublicAPI (or > .internal package) so consumers could distinguish "Calcite's internal > utility class" from "true public API (as in semver)". > > That however did not get much attention. It turned out we somehow > managed to live without it. > I do not find lots of questions on the list on the subject, thus > current approach seems to be good enough. > > I wonder if that would be a good starter / newbie jira issue. > > Vladimir
