*bq. a list of all breaking changes between 1.15.0 and the latest 1.15.x (or intermediate releases)* Yes, this might help users to be more prepared before upgrading, if they could know whether need to recompile their applications. Asking about 1.14/1.15 since they are the "in service" versions.
But it's totally fine if we're targeting for the future (smile). Best Regards, Yu On Wed, 31 Aug 2022 at 21:41, Chesnay Schepler <ches...@apache.org> wrote: > Well then someone didnt update the FLIP number as they should! > I'll increment the number of this FLIP to 255. > > On 31/08/2022 15:06, Matthias Pohl wrote: > > +1 for bringing this into a consistent state. Thanks, Chesnay. > > > > nit: There's a conflict between this FLIP-254 and the FLIP-254 on the > redis > > streams connector. > > > > On Wed, Aug 31, 2022 at 2:52 PM Chesnay Schepler <ches...@apache.org> > wrote: > > > >> * backport to 1.14/1.15 > >> > >> On 31/08/2022 14:45, Chesnay Schepler wrote: > >>> @Yu I haven't really considered 1.14/1.15. > >>> > >>> What exactly are you interested in; a list of all breaking changes > >>> between 1.15.0 and the latest 1.15.x (or intermediate releases), > >>> or are you suggesting to also backport this whole thing to 1.16 (which > >>> should be possible)? > >>> > >>> On 31/08/2022 13:31, Yu Li wrote: > >>>> +1 for the FLIP. Thanks for the efforts Chesnay. > >>>> > >>>> I believe ensuring binary compatibility for patch releases will also > >>>> benefit our end users besides the cloud service providers. > >>>> > >>>> I'm also wondering about the compatibility checking result after > >>>> enabling > >>>> japicmp for all modules with existing patch releases (1.14.x and > >>>> 1.15.x). > >>>> Do you already have one with your local customized japicmp or do we > >>>> need to > >>>> wait until the works tracked in JIRA are done? (smile) > >>>> > >>>> Best Regards, > >>>> Yu > >>>> > >>>> > >>>> On Wed, 31 Aug 2022 at 18:50, Konstantin Knauf <kna...@apache.org> > >>>> wrote: > >>>> > >>>>> Hi Chesnay, > >>>>> > >>>>> thanks for bringing this up and for your research and fixes to > japicmd. > >>>>> > >>>>> +1 for the proposal. For Immerok as an Apache Flink cloud service > >>>>> provider > >>>>> it is very valuable to know that our users don't need to upgrade > >>>>> their Jobs > >>>>> when the Flink patch version changes. I am sure the same is true for > >>>>> internal platform teams as well as end users of Apache Flink. > >>>>> > >>>>> Cheers, > >>>>> > >>>>> Konstantin > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Am Mi., 31. Aug. 2022 um 12:31 Uhr schrieb Chesnay Schepler < > >>>>> ches...@apache.org>: > >>>>> > >>>>>> Hello, > >>>>>> > >>>>>> I just published a FLIP to guarantee binary compatibility for patch > >>>>>> releases. I don't think our current guarantees of > source-compatibility > >>>>>> are sufficient for patch releases. > >>>>>> > >>>>>> > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857 > >>>>>> Let me know what you think. > >>>>>> > >>>>>> Regards, > >>>>>> Chesnay > >>>>>> > >>>>> -- > >>>>> https://twitter.com/snntrable > >>>>> https://github.com/knaufk > >>>>> > >> > >
