I think Jun's patch is minimally invasive and solves an important bug. So I will roll an RC3 today (sigh :). Let's do a shorter RC cycle this time, though, and plan to start a vote for release Friday.
-Jonathan On Tue, Jun 23, 2009 at 11:34 AM, Jun Rao<jun...@almaden.ibm.com> wrote: > Under heavy load and large column values (10s of Ks), we observed that > cassandra TCP channels can get jammed. A new patch is provided to > https://issues.apache.org/jira/browse/CASSANDRA-220. > > I see two options: > 1) patch #220 to 0.3.0 and release RC3 > 2) release RC2 with a release note that describes the above potential > problem. > > What do people feel? > > Jun > IBM Almaden Research Center > K55/B1, 650 Harry Road, San Jose, CA 95120-6099 > > jun...@almaden.ibm.com > > Jonathan Ellis <jbel...@gmail.com> > > > Jonathan Ellis <jbel...@gmail.com> > > 06/22/2009 08:14 AM > > Please respond to > cassandra-dev@incubator.apache.org > > To > cassandra-dev@incubator.apache.org > cc > > Subject > VOTE: Cassandra 0.3.0 release > > It's been two weeks since the last code change on the 0.3 branch and > several days since RC2 release with no new bug reports. > > I move that we release RC2 as 0.3.0 official. > > svn tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.3.0-rc2/ > > binary build: > http://people.apache.org/~jbellis/cassandra/cassandra-0.3.0-rc2.tar.gz > > Voting will run for 3 days. > > +1 from me. > > -Jonathan > >
