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 stuhood@mailtrust.com
 designates 207.97.245.231 as permitted sender)
Date: Sun, 25 Jul 2010 15:13:43 -0500 (CDT)
Subject: =?UTF-8?Q?Re:=20Almost=20time=20for=200.7=20beta=3F?=
From: "Stu Hood" <stu.hood@rackspace.com>
To: dev@cassandra.apache.org
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
In-Reply-To: <460EB885-8787-46D0-B14F-D7DBD05CA6A6@chrisgoffinet.com>
References: <AANLkTi=kK_P1+SJvj=vtiz6nF9rT41HJhtJdSU-gZ+z4@mail.gmail.com>
 <460EB885-8787-46D0-B14F-D7DBD05CA6A6@chrisgoffinet.com>
Message-ID: <1280088823.588210836@192.168.2.229>

The are a few tickets affecting the public API that Rackspace would really =
like to see make it into the 0.7-beta, since they will be very difficult to=
 apply once a mass of people have gone through the readTablesFromYaml proce=
ss.=0A=0AIn particular, we'd like to see 1066, 1237 and the portion of 1271=
 modifying AccessLevel block 0.7-beta, but we're fairly certain these can b=
e knocked out this week.=0A=0AThanks,=0AStu=0A=0A-----Original Message-----=
=0AFrom: "Chris Goffinet" <cg@chrisgoffinet.com>=0ASent: Saturday, July 24,=
 2010 9:56pm=0ATo: dev@cassandra.apache.org=0ACc: cassandra-dev@incubator.a=
pache.org=0ASubject: Re: Almost time for 0.7 beta?=0A=0A+1. Digg has been h=
olding off until at least beta before testing. I'd love to start this as so=
on as possible.=0A=0A-Chris=0A=0AOn Jul 24, 2010, at 7:49 PM, Jonathan Elli=
s wrote:=0A=0A> At the time of our last update [1], I estimated it would be=
 4 to 6=0A> weeks until a 0.7 beta.  That was over 8 weeks ago.  Although w=
e've=0A> never adhered to a strict release schedule, I'm feeling more and m=
ore=0A> like we need to stop delaying getting what is already done into=0A>=
 peoples' hands.=0A> =0A> Wide row support was the main "blocker" in my min=
d for 0.7, and that=0A> was complete a month ago. [2]  Basic secondary inde=
x support will be=0A> also be done in the next few days (see subtasks to [3=
]).  I propose=0A> rolling a beta release next Friday and a release candida=
te two weeks=0A> after that; anything not ready at that point can wait unti=
l 0.7.1 or=0A> 0.8.=0A> =0A> The bad news is, vector clocks [4] and the Avr=
o client api [5] will=0A> probably not be ready for the beta but may be rea=
dy for the release=0A> candidate.  I would be okay putting those directly i=
nto the RC since=0A> they are completely optional and will not affect users=
 who want to=0A> ignore them.  (That is, more than they already have, with =
the Clock=0A> struct in the Thrift API.)  But I don't want to slip the sche=
dule any=0A> more to wait for them.=0A> =0A> [1] http://www.mail-archive.co=
m/dev@cassandra.apache.org/msg00404.html=0A> [2] https://issues.apache.org/=
jira/browse/CASSANDRA-16=0A> [3] https://issues.apache.org/jira/browse/CASS=
ANDRA-749=0A> [4] https://issues.apache.org/jira/browse/CASSANDRA-580=0A> [=
5] https://issues.apache.org/jira/browse/CASSANDRA-926=0A> =0A> -- =0A> Jon=
athan Ellis=0A> Project Chair, Apache Cassandra=0A> co-founder of Riptano, =
the source for professional Cassandra support=0A> http://riptano.com=0A=0A