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 jbellis@gmail.com designates
 74.125.82.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=pfWPwsmz+jKf6RzSk0f0UPxzwdbGHX7X+3pUqLb43hSA9LzFBRWkvc88oJZZewLqwf
         Pn/5xEG3+WQ99obNF1AGe8+Vs2uj30jWya260AUBVErvqxOwDDsMazAf8sht2cRioDV5
         Le+lhNOQEE1G0Vgb+j4qP1sBHk00JTnGkYv9g=
MIME-Version: 1.0
In-Reply-To: <1307434113.5724.47.camel@erebus.lan>
References: <1307434113.5724.47.camel@erebus.lan>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 7 Jun 2011 08:18:49 -0500
Message-ID: <BANLkTi=noF0sC-R0GUzuKa9jQbH_ZGZcOw@mail.gmail.com>
Subject: Re: Reoganizing drivers
To: dev@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sounds fine as far as it goes, but don't we want some concept of
branches/tags for driver releases too?

On Tue, Jun 7, 2011 at 3:08 AM, 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. =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. =A0There are a number of reasons why, not least of which is
> 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
> | =A0|- java
> | =A0|- py
> | =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?
>
>
> --
> Eric Evans
> eevans@rackspace.com
>
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com