No, but we will definitely take a look at it for 0.5.1. 0.5.0 will not be perfect but it is a huge improvement over 0.4.2, which people are still using because that's the official "stable" release. We need to fix that. :)
-Jonathan On Mon, Jan 18, 2010 at 6:39 PM, Ryan Daum <r...@thimbleware.com> wrote: > Any chance of https://issues.apache.org/jira/browse/CASSANDRA-713 getting > looked at and closed before a 0.5.0 final? > > On Mon, Jan 18, 2010 at 7:32 PM, Pablo A. Delgado <pabl...@gmail.com> wrote: > >> +1 >> >> On Tue, Jan 19, 2010 at 1:19 AM, Jaakko <rosvopaalli...@gmail.com> wrote: >> >> > +1 >> > >> > >> > On Tue, Jan 19, 2010 at 5:28 AM, Eric Evans <eev...@rackspace.com> >> wrote: >> > > >> > > There have been a few changes[1] in the 0.5 branch since RC3. In a >> > perfect >> > > world, we'd probably push those into another release candidate, but I >> > > feel pretty good about this one, and any remaining issues can always >> > > be added to 0.5.1. >> > > >> > > I propose the following tag and artifacts for 0.5.0: >> > > >> > > SVN Tag: >> > > >> > >> https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0 >> > > 0.5.0 artifacts: http://people.apache.org/~eevans >> > > >> > > +1 from me. >> > > >> > > >> > > [1] >> > > >> > >> https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0/CHANGES.txt >> > > >> > > -- >> > > Eric Evans >> > > eev...@rackspace.com >> > > >> > > >> > >> >