Putting End-of-Life for old Hudi versions

[xushiyan]

We encourage people to move to more recent versions. To align with this, we should also define end-of-life (EOL) for old releases. Some model like python is using: https://devguide.python.org/versions/

We only need to do 3 support level:

• Active: actively developed versions
• Bug fix: only for fixes, incl. security fix, not adding any feature or changing any behavior (except for fixing a bug). only patch releases can be made (X.Y.Z -> X.Y.Z+1)
• EOL (not supported, no more patch releases, users should upgrade)

Can we start with putting EOL on versions prior to 0.14 (table version 6) ?

[xushiyan]

It can be something to be published in https://endoflife.date/ too.

[danny0405]

+1

[vinothchandar]

Also may be remove it from maven/artifactory to clear up storage space?

[nsivabalan]

+1 as well.

[voonhous]

+1.

[suryaprasanna]

+1 too.
What is the plan, do we want to go with a fixed time range for each release that we want to support, i.e. let's say a version will be supported for 2 years from release date? Or will the expiry of versions depends on version to version?

[yihua]

+1

[xushiyan]

the EOL release docs have been removed (#14217). artifact cleanup needs separate follow-up with ASF. closing this now. thanks everyone for commenting. Will also be making an announcement in mailing lists about this.