THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Patch releases not having binary compatibility is problematic for everyone:
- users (including service offerings) 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, 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.".
...