I don't think we can script this (yet) in the release process, because the
actual releasing (as opposed to the candidate creation process) is not
automated.
I just updated the
https://cwiki.apache.org/confluence/display/FLINK/Releasing guide and
included the japicmp Flink reference version change
Robert,
I was going to file a ticket but posted to the mailing list and was hoping for
your input.
That may be the wrong configuration option but what I was thinking is that:
- 1.3.0 should have a compatible API relative to 1.2.0 (no modifications, only
additions)
- 1.2.1+ should have the same
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 "breakBuildOnModificatio
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
