Hi everyone, As promised, here is the follow-up FLIP [1] for discussing how we can ensure that newly introduced APIs are being stabilized over time. This FLIP is related to FLIP-196 [2].
The idea of FLIP-197 is to introduce an API graduation process that forces us to increase the API stability guarantee unless there is a very good reason not to do so. So the proposal is to reverse the process from opt-in (increasing the stability guarantee explicitly) to opt-out (deciding that an API cannot be graduated with a good reason). Since every process breaks if it is not automated, we propose a richer set of API stability annotations that can capture enough information so that we can implement a test that fails if we fail to follow the process. Looking forward to your feedback. Hopefully, we can provide our users a better experience when working with Flink because we offer more stable APIs and make them available faster. [1] https://cwiki.apache.org/confluence/x/J5eqCw [2] https://cwiki.apache.org/confluence/x/IJeqCw Cheers, Till
