[openstack-dev] SQLAlchemy-migrate needs a new maintainer

Monty Taylor mordred at inaugust.com
Thu Jul 11 23:29:16 UTC 2013

On 07/11/2013 03:12 PM, Monty Taylor wrote:
> On 07/11/2013 02:40 PM, David Ripton wrote:
>> OpenStack is currently divided.  Older projects like Nova use
>> sqlalchemy-migrate.  Some newer projects like Neutron use alembic.
>> I'd personally like to see everything in Alembic, but migrating all the
>> Nova scripts in a way that didn't break compatibility will be a big
>> challenge.  It's easier for projects with less to port.
>> Another option is to take over maintaining sqlalchemy-migrate and bend
>> it to our needs.  (It's mostly okay, but the big issue for me is its use
>> of strictly incrementing integer sequence numbers.  That both causes
>> problems when competing patches in review race for the same filename,
>> and when we try to backport some but not all migration scripts to a
>> stable branch.)  We already apply some patches to upstream, so having a
>> friendly maintainer who would apply patches that OpenStack needs would
>> be helpful.
>> This will be a topic at the DB meeting today at 1900 UTC (about 20
>> minutes from when I send this email).  So please attend if it's
>> important to you.
>> On 07/11/2013 02:18 PM, Thomas Goirand wrote:
>>> Discussing with Jan Dittberner, who is upstream for sqlalchemy-migrate,
>>> it appears that he doesn't have time to maintain it.
>>> Is the OpenStack project willing to take over? Jan is ok to hand over
>>> everything, moving to Github, give access to Pypi, etc. Below is his
>>> reply to me when I asked him.
> Hi - We discussed this in the db meeting and decided that as much as
> we're not thrilled with sqlalchemy-migrate (I believe boris-42 summed it
> up as "bad bad bad very bad things") we've got a pretty strong
> dependency on it right now and for the next while.
> SO - let's work on getting it moved into our systems and then we at
> least have the ability to patch/release if needed.

We've got the upstream pypi and rtfd credentials now, the project should
be moved in to openstack systems soon enough. I also went through and
cleaned up build and test stuff work work like our stuff works (if we're
going to be maintaining it, we might as well, you know, do it how we do

This brings us to the most important question:

Who wants to be on the core team?

>>> Or is the OpenStack project moving toward Alembic as well?
>>> Thoughts anyone?
>>> Thomas Goirand (zigo)
>>> On 07/12/2013 01:27 AM, Jan Dittberner wrote:
>>>> I would be very happy to hand over the maintenance of
>>>> sqlalchemy-migrate to
>>>> a team that actually uses it. At the moment I take care of the Google
>>>> Code
>>>> [1] project for sqlalchemy-migrate and maintain a Jenkins instance at
>>>> http://jenkins.gnuviech-server.de/. I'm all in favour of moving to
>>>> github,
>>>> Google Code was just choosen because it was available at the time the
>>>> project moved from the initial developer's (Evan Rosson) personal
>>>> server. I
>>>> can also give access to the PyPI project page [2] to a prospective new
>>>> maintainer/team.
>>>> I wrote some sphinx documentation and improved the tests a while ago
>>>> but I
>>>> have no time to maintain it properly. I switched to alembic for my small
>>>> personal projects.
>>>> [1] https://code.google.com/p/sqlalchemy-migrate/
>>>> [2] https://pypi.python.org/pypi/sqlalchemy-migrate
>>>> Best regards
>>>> Jan
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list