Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of gdusbabek@gmail.com
 designates 209.85.212.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=e96HdF95FDfEb4n+ypDa1GcV+Pem/QxM5D3ikBJuBm02cNkyji07OICRpn3Z2plTQ7
         xBKQNxzYentG65xhqLUCWYLzqIZ9xKMHHD6RJqsxyNWwOC+7gJqn+mOofvDLT/vk2Bgx
         WQeGfySynNS6A8R/ZvVjHlTzYLTo+IfbMrOmE=
MIME-Version: 1.0
Reply-To: gdusbabek@gmail.com
In-Reply-To: <1307434113.5724.47.camel@erebus.lan>
References: <1307434113.5724.47.camel@erebus.lan>
Date: Tue, 7 Jun 2011 07:26:59 -0500
Message-ID: <BANLkTi=f=3emSjZqeUucX126tYPtO9FY+Q@mail.gmail.com>
Subject: Re: Reoganizing drivers
From: Gary Dusbabek <gdusbabek@gmail.com>
To: dev@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 7, 2011 at 03:08, Eric Evans <eevans@rackspace.com> wrote:
>
> Sylvain and I have been discussing release issues while here at
> buzzwords, and some of the issues are related to drivers. =C2=A0Not
> surprising since that's a new concept for us, and there wasn't much
> thought given to the current organization.
>
> Because the CQL drivers are independently versioned and capable of
> releasing on their own timelines, the current location in SVN is
> suboptimal. =C2=A0There are a number of reasons why, not least of which i=
s
> that it sets the expectation that the correct version of a driver is
> whatever corresponds to the release version of Cassandra.
>
> So, we'd like to move the drivers sub-directory up one level, making it
> look something like the following:
>
> |- branches
> |- tags
> |- site
> |- drivers
> | =C2=A0|- java
> | =C2=A0|- py
> | =C2=A0|- txpy
> |- trunk
>
> There are a few additional implied changes here as well, for example the
> JDBC driver will need its own build, and Cassandra's will need some
> minor changes as well (JDBC driver tests, release artifacts, etc).
>
> Does anyone object to this?

Not me.  +1 to the idea of breaking the drivers out.

Gary.


>
>
> --
> Eric Evans
> eevans@rackspace.com
>
>