Hi Jing, I think it's fine to update the table to include lesser versions, as long as we provide a link to an older version of the table, for users who might be trying to upgrade from an older Flink version to the latest, so that they are aware of potential issues that could run into.
Best regards, Martijn On Thu, Sep 14, 2023 at 10:22 PM Jing Ge <j...@ververica.com.invalid> wrote: > Hi, > > According the community update policy[1] for old releases, there is another > cleaner option: > > option 3: only keep the last three versions. > > Compatibility info of older versions could still be found in the old > releases. > > If there are no concerns, the upcoming 1.18 release will choose option 3 > which aligns with the community's support policy. > > Best regards, > Jing > > [1] https://flink.apache.org/downloads/#update-policy-for-old-releases > > On Thu, Sep 14, 2023 at 1:03 PM Jing Ge <j...@ververica.com> wrote: > > > Hi folks, > > > > The compatibility table[1] contains old Flink versions. Does it make > sense > > to clean up and remove some very old versions? My proposal would be: > > > > option 1: keeping less than the last 10 versions in this table so that in > > most cases reader does not need to scroll to the right to read hidden > > columns. > > option 2: remove versions older than 1.8.x, since their savepoints are > not > > compatible with 1.17.x (the last release). > > > > If we could reach a consensus, it will go into effect immediately with > the > > master branch and the upcoming 1.18 release. > > > > Looking forward to your feedback and votes. > > > > > > Best regards, > > Jing > > > > [1] > > > https://nightlies.apache.org/flink/flink-docs-master/docs/ops/upgrading/#compatibility-table > > > > > > >
