Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of eevans@acunu.com designates
 209.85.213.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL35Oi3_+OW0t4rTnY6dTeuVfBhSXw13niMux_m2CLW0jpOL7w@mail.gmail.com>
References: 
 <CAL35Oi3_+OW0t4rTnY6dTeuVfBhSXw13niMux_m2CLW0jpOL7w@mail.gmail.com>
Date: Wed, 14 Sep 2011 09:24:16 -0500
Message-ID: 
 <CAL35Oi1=k9002DH1tOKFY945ZmkSoyQSzpaL8LgM7xVvUkzYZA@mail.gmail.com>
Subject: Re: Proposal: Moving CQL drivers
From: Eric Evans <eevans@acunu.com>
To: dev@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 6, 2011 at 12:20 PM, Eric Evans <eevans@acunu.com> wrote:
> 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

To update this, the Python driver should be ready to go.  I've create
an Apache Extras project, and imported the code (including an revised
copy of test_cql.py).

The JIRA issue for this is
https://issues.apache.org/jira/browse/CASSANDRA-3180.  Once it has
passed review (help with this appreciated) we can remove the driver
from trunk and proceed to the JDBC driver.

Thanks.

--=20
Eric Evans
Acunu |=A0http://www.acunu.com=A0| @acunu