For the lazy and the archives, the links to the mentioned tickets: The big ones:
https://issues.apache.org/jira/browse/CASSANDRA-185 https://issues.apache.org/jira/browse/CASSANDRA-240 https://issues.apache.org/jira/browse/CASSANDRA-303 https://issues.apache.org/jira/browse/CASSANDRA-304 Call it good for 0.4: https://issues.apache.org/jira/browse/CASSANDRA-232 https://issues.apache.org/jira/browse/CASSANDRA-300 On Mon, Jul 20, 2009 at 8:10 PM, Jonathan Ellis<[email protected]> wrote: > Well, that was a long "week." My fault -- as I commented on IRC, I > underestimated how long 185 would take as badly as I can remember > doing anywhere. > > We're done with the big ones now. (185, 240, 303, and 304). > > Two more and then I think we can call it good for 0.4 from the > client's perspective: 232 and 300 (dealing with specifying the number > of replicas to wait for when reading/writing, respectively) > > -Jonathan > > On Wed, Jul 8, 2009 at 1:47 PM, Jonathan Ellis<[email protected]> wrote: >> Hi all, >> >> Just a heads up that this is going to be The Week Of Breaking Things >> in the client api. There are a bunch of long-standing problems that >> can't be fixed without making fundamental changes in the API so we are >> going to bite the bullet and get those done now. We've already done >> CASSANDRA-261, -277, and -280; next up will be CASSANDRA-139, and >> eventually CASSANDRA-240 and friends. >> >> If you're on a version of trunk that Works For You, you might want to >> resist the urge to svn up until the dust settles. >> >> -Jonathan >> >
