So following on from the previous discussion[1] about moving the CQL drivers out of tree, my interpretation of that discussion is that we have consensus that this should be done, and that they should go in Google Code and Apache Extras. Further, it seems a foregone conclusion that Git be used, and so I also assume that's a safe assumption, at least for the two existing drivers (Python and Java).
One of the obstacles was the tight coupling of components that the JDBC driver depends on, which should now be solved in trunk (https://issues.apache.org/jira/browse/CASSANDRA-2936). Other than that the only items remaining relate to updating the tests so that they can connect to an already running instance, instead of the setup/teardown of nodes that is done now. Here is what I propose to do (one driver at a time): 1. Setup new Git-based projects on Apache Extras (cassandra-jdbc and cassandra-dbapi2) 2. Import the most current code and fix-up the tests as needed 3. Submit issues w/ patches for the removal of the corresponding driver from Cassandra I would like to have this in place for 1.0, and believe it should be OK despite the fact that we are freezing on September 8 (we're still freezing on 9/8 I assume?). Since the plan was to delete the drivers directory after branching anyway, this shouldn't be disruptive to the release (even if drivers/ weren't deleted, the only functional change would be to remove JDBC build and test targets from build.xml). Thoughts? [1]: http://thread.gmane.org/gmane.comp.db.cassandra.devel/4075 -- Eric Evans Acunu | http://www.acunu.com | @acunu
