Thanks for bringing this up for discussion Piotr. One the one hand I think it's a good idea, because of the reasons you've mentioned. On the other hand, having an LTS version will remove an incentive for some users to upgrade, which will result in fewer Flink users who will test new features because they wait for the next LTS version to upgrade. I can see that particularly happening for large enterprises. Another downside I can imagine is that upgrading from one LTS version to another LTS version will become more complicated because more changes have been made between those versions.
Related to my second remark, would/could introducing an LTS version would also trigger a follow-up discussion that we could potentially introduce breaking changes in a next LTS version, like a Flink 2.0 [1] ? Best regards, Martijn [1] https://issues.apache.org/jira/browse/FLINK-3957 On Fri, 12 Nov 2021 at 08:59, Fabian Paul <fabianp...@ververica.com> wrote: > Thanks for bringing up this topic Piotr. > I also think we should try to decouple our release cycles from our support > plans. Currently we are very limited by the approach because faster release > cycles result in also faster deprecation of versions. > > > Therefore I am also favoring version 2 where we can align the next LTS > version > with our development speed. Option 1 I think can easily lead to confusion > when > the number of supported releases constantly changes. > > Best, > Fabian > >
