Status

Current state: Under discussion

...

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Flink currently only provides source-compatibility across releases, including patch versions.

...

users can't just redeploy Flink but have to rebuild their jobs, usually not actually requiring changes
connector/library authors need to create a new release for every Flink patch release (where nothing is supposed to change), usually not actually requiring changes
with the externalization of connectors we'd turn even a small patch release into a 10+ vote ordeal
- that one could only avoid by technicalities ("this release does not have breaking changes so we don't need to create a new release") which would weaken the general messaging around compatibility, as it would eventually in turn into "just use your old jars; you'll be fine...probably.".

No public interfaces are affected by the change

Enable Japicmp in all modules (

Jira

) and do not add exclusions in the release branches after 1.X.0.

...

The version is functionally identical with Japicmp 1.16.0; it just downgrades the Maven dependency to 3.2.5.

not applicable

Japicmp + checks by the Release Manager that no exclusions were added.

no rejected alternatives considered