discuss: Upgrade python binding building image to manylinux_2_28 instead

[Xuanwo]

Hi, as mentioned in #5483, it seems unlikely that we can resolve this issue without upgrading the GCC version used for compilation. Perhaps it's time to drop the old manylinux2014 and switch to manylinux_2_28 instead.

This change will update our minimum compatible glibc version to 2.28.

Our old version is manylinux2014, which targeted to CentOS 7 based, glibc 2.17, supports the following:

• Debian 8+
• Ubuntu 13.10+
• Fedora 19+
• RHEL 7+

The new version will be manylinux_2_28, which targeted to AlmaLinux 8 based, glibc 2.28, supports the following:

• Debian 10+
• Ubuntu 18.10+
• Fedora 29+
• CentOS/RHEL 8+

What do you think?

• +1: I support this idea, ....
• 0
• -1: I don't like this idea, since...

[Zheaoli]

I prefer upgrade to manylinux_2_28

[messense]

x86 can stay on manylinux2014, upgrade to 2_28 for aarch64 is fine given that arm64 system only becomes popular in recent years.

[Xuanwo]

That makes sense as well. The only drawback is that our release workflow becomes a bit more complex.

Would you like to implement this change?

[messense]

#5522

[Xuanwo]

Thank you very much for the quick PR!