On Sep 2, 2013, at 10:28 AM, jank <[email protected]> wrote:
> Hello, > > I am about to release a dialect for EXASol DB (http://www.exasol.com) on > GitHub. > > I have read the docs regarding participation and development. I am also aware > that new dialects should reside in their own project: > http://docs.sqlalchemy.org/en/latest/dialects/index.html > > Questions that remain are: > are there any places where the new dialect should be announced (apart from > this list)? hmmm, nothing official, pypi, SQLAlchemy list, tweets? if EXASol itself has some kind of user list, that would be good > can/should/must the sqla jenkins be used for integration testing? well in this area its like a "definite maybe". jenkins currently runs build slaves on an amazon cloud (the master is hosted on a Linode) and more backends means more test suites to run and more server time, which I pay for with the help of a good deal of gittip income. in the current setup, the target database has to run on an AWS node of some kind. I've been told that Rackspace has been giving projects free hosting though I have some reservations about that, including how hard it would be to get the whole jenkins environment to use rackspace instead of AWS without any hiccups (I've spent months getting AWS to run smoothly including submitting two patches to Jenkins itself). Currently I don't know that I have a clean way for the main SQLA Jenkins server to run arbitrary remote tests elsewhere, maybe some of the other testing services like travis have some solution to that (I really love jenkins though and am not ready to give it up). so perhaps where I'm at is "suggestions welcome".
signature.asc
Description: Message signed with OpenPGP using GPGMail
