On Tue, Sep 24, 2024, at 2:49 PM, jay@gr-oss.io wrote:
On 9/24/24 12:54 PM, Thomas Goirand <zigo@debian.org> wrote:
Hi,
As much as I know, there's no active OpenStack project using sqlalchemy- migrate anymore. Can someone retire the project, or at least push some indication in the README.rst that the project is retired? When looking at:
https://opendev.org/x/sqlalchemy-migrate
nothing says so...
I agree it'd be nice for someone to retire this, but as it's an "x" namespaced project, it's not under OpenStack governance. I'd strongly suggest anyone who has access and authority to take this action.
You can see the current group membership with the authority to merge changes to the repo here in sqlalchemy-migrate-core Gerrit group [0]. Good news at least three of the five members are still active openstack developers including Zigo. Digging around with hound [1] it looks like some things may still be using sqlalchemy-migrate (Airship for example maybe?). That also only searches the default branch of each repo so you may also want to double check that no stable branches rely on it any longer as well. Of course retiring the repo doesn't affect the packages on PyPI (which get half a million downloads a month [2]), but fixing critical issues might become more painful if retired. Maybe the best thing to do is try and communicate the deprecation and move people to alembic via README/docs updates as well as potentially a new release that raises a deprecation warning when invoked? [0] https://review.opendev.org/admin/groups/4902511a495e67cc7938fb06ac1349a1be3e... [1] https://codesearch.opendev.org/?q=sqlalchemy-migrate&i=nope&literal=nope&files=&excludeFiles=&repos= [2] https://pypistats.org/packages/sqlalchemy-migrate