On 10/11/23 2:30 PM, Ghanshyam Mann wrote: [snip]
But this is what we agreed in the below change in policy to keep python min version as much as we can. - https://review.opendev.org/c/openstack/governance/+/882154
I don't think dropping python 3.8 support for 2024.1 violates that agreement. Lines 35-38: Projects should avoid removing Python versions that have not reached `End Of Life <https://devguide.python.org/versions/>`_ without a solid reason. It is recommended to keep compatability with older Python versions as long as possible. What we're disagreeing about is what counts as "a solid reason". The only distro mentioned anywhere in the "Tested Runtimes for 2024.1" document [0] that has python 3.8 as the default is Ubuntu 20.04, and we can't run master (2024.1 development) devstack on it. That strikes me as "a solid reason" not to support python 3.8 in 2024.1. Adding the fact that python 3.8 will stop receiving security fixes within 6 months of the 2024.1 release makes this reason even more solid.
Again, this is very low expectation on keeping/testing python3.8 which is to run the unit or functional tests so that we make sure we do not break installation or code error for python3.8. This is not very costly for upstream but a good help for users on older python.
Sure, but the governance patch you reference above is not the only consideration. The "2018-10-24 Python Update Process" [1] TC resolution has not been superseded by any other resolution, and dropping python 3.8 support in 2024.1 does not violate the three criteria set out there. (With respect to criterion 2, Ubuntu 20.04 is *not* listed in the targeted distributions section of [0].) In any case, I don't think the proposal to drop python 3.8 support violates previous agreements by the TC. [0] https://governance.openstack.org/tc/reference/runtimes/2024.1.html [1] https://governance.openstack.org/tc/resolutions/20181024-python-update-proce...