Hi Greg, I was not able to update the version to 1.2.0 when updating to 1.3-SNAPSHOT, because 1.2.0 was not released at that point in time :) But I agree that we should update that version once the release is out. I forgot to do it.
I'm not sure if I completely understand "breakBuildOnModifications". Does it fail the build even if somebody did a change that is non API breaking on a @Public class? On Thu, Mar 16, 2017 at 3:37 PM, Greg Hogan <c...@greghogan.com> wrote: > Hi, > > I see in the parent pom.xml that 1.3-SNAPSHOT is checking for API > stability against 1.1.4. Also, that this version was only bumped with > FLINK-5617 late in the 1.2 development cycle. > > Should we bump this version as part of the release process, i.e. on the > 1.2.0 release updating 1.3-SNAPSHOT to verify against 1.2.0? And should we > be setting ‘breakBuildOnModifications’ [0] to true for patch releases > (overridden when necessary)? > > [0] https://siom79.github.io/japicmp/MavenPlugin.html > > Greg
