I don't know what's all involved in putting out a release for
sqlalchemy-migrate but if there is a way that I can help, please let me
know. I'll try to catch dripton in IRC today.
As for CI with DB2, it's in the blueprint as a work item, I just don't
know enough about the infra side of things to get that going, so I'd
need some help there.
DB2 Express-C is the free version which is the plan to run the unit
tests in CI, but the only problem I see with that is it's a trial
license and I wouldn't want to have to redo images or licenses every 3
months or however long it lasts. I would think that IBM would be able to
provide a permanent license for CI though, otherwise our alternative is
running the tests in-house and reporting the results back (something
like what the nova virt drivers have to do and vmware is already doing).
Thanks,
Matt Riedemann
On 11/12/2013 1:50 AM, Roman Podoliaka wrote:
Hey David,
Thank you for undertaking this task!
I agree, that merging of DB2 support can be postponed for now, even if
it looks totally harmless (though I see no way to test it, as we don't
have DB2 instances running on Infra test nodes).
Thanks,
Roman
On Mon, Nov 11, 2013 at 10:54 PM, Davanum Srinivas <dava...@gmail.com> wrote:
@dripton, @Roman Many thanks :)
On Mon, Nov 11, 2013 at 3:35 PM, David Ripton <drip...@redhat.com> wrote:
On 11/11/2013 11:37 AM, Roman Podoliaka wrote:
As you may know, in our global requirements list [1] we are currently
depending on SQLAlchemy 0.7.x versions (which is 'old stable' branch
and will be deprecated soon). This is mostly due to the fact, that the
latest release of sqlalchemy-migrate from PyPi doesn't support
SQLAlchemy 0.8.x+.
At the same time, distros have been providing patches for fixing this
incompatibility for a long time now. Moreover, those patches have been
merged to sqlalchemy-migrate master too.
As we are now maintaining sqlalchemy-migrate, we could make a new
release of it. This would allow us to bump the version of SQLAlchemy
release we are depending on (as soon as we fix all the bugs we have)
and let distros maintainers stop carrying their own patches.
This has been discussed at the design summit [2], so we just basically
need a volunteer from [3] Gerrit ACL group to make a new release.
Is sqlalchemy-migrate stable enough to make a new release? I think,
yes. The commits we've merged since we adopted this library, only fix
a few issues with SQLAlchemy 0.8.x compatibility and enable running of
tests (we are currently testing all new changes on py26/py27,
SQLAlchemy 0.7.x/0.8.x, SQLite/MySQL/PostgreSQL).
Who wants to help? :)
Thanks,
Roman
[1]
https://github.com/openstack/requirements/blob/master/global-requirements.txt
[2] https://etherpad.openstack.org/p/icehouse-oslo-db-migrations
[3] https://review.openstack.org/#/admin/groups/186,members
I'll volunteer to do this release. I'll wait 24 hours from the timestamp of
this email for input first. So, if anyone has opinions about the timing of
this release, please speak up.
(In particular, I'd like to do a release *before* Matt Riedermann's DB2
support patch https://review.openstack.org/#/c/55572/ lands, just in case it
breaks anything. Of course we could do another release shortly after it
gets in, to make folks who use DB2 happy.)
--
David Ripton Red Hat drip...@redhat.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Davanum Srinivas :: http://davanum.wordpress.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
