I think the C changes were just exposing additional APIs, so there should be no backwards compatibility implications.
best, On Mon, May 8, 2017, at 12:48, Mike Drob wrote: > Had a chance to look at this in more detail. From the Java side we should > be safe to do 4.2.1. From the C side... I don't know what kind of > guarantees we offer there. Looks like addition of APIs, but I don't know > what C communities and users expect. > > Colin and Masatake - since you were involved in the change, can you > comment? > > Mike > > On Mon, May 8, 2017 at 9:14 AM, Raam Rosh-Hai <[email protected]> wrote: > > > Doesn't seem like any api changes were made so I am for the sneaking in a > > minor version > >
