On 5/31/24 10:13, Pierre Riteau wrote:
While all projects must be compatible with the upper constraint (currently 2.0.30), should we agree on a maximum version for the lower bound? The 2024.2 release targets Ubuntu Jammy, which includes python3-sqlalchemy 1.4.31, and Debian bookworm, which includes python3-sqlalchemy 1.4.46.
Hi Pierre,
Thanks for bringing this topic in the list. I've been watching the developments of SQLA 2.x support very closely myself as well.
I shall remind everyone that while the gate has some upper constraints, "agreeing on them" doesn't work for me (as the package maintainer in Debian) if what's agreed upon is in direct conflict with what's in Debian unstable, where I'm doing my packaging. As a reminder, SQLAlchemy is in version 2.0.30 right now in Debian Unstable, which makes a number of project to fail:
https://qa.debian.org/excuses.php?package=sqlalchemy
For OpenStack, here's the (shorter list) of problematic projects: - trove - zaqar
It was a big relief to see all of the other projects fixed one by one. Thanks to everyone doing it, and especially Stephen for the amount of work he has put into it.
I'm well aware that these 2 remaining projects may be in bad shape in OpenStack upstream anyways: this is another a sign of their bad health. Everything else that is still in Debian was fixed (I removed many that we declared unmaintained recently :( ).
Therefore, I am of the opinion that we should impose SQLA 2.x in our global requirements ASAP, and put the pressure on these 2 remaining projects to be fixed, or simply declare them as not maintained anymore, unfortunately.
I really hope Trove was maintained better, it'd be a huge disappointment if we were to decide it's not maintained, but closing our eyes will not help our users.
Cheers,
Thomas Goirand (zigo)