Sorry to be That Guy, but CASSANDRA-3733 (just fixed by Brandon) can
cause OOM during hint replay similar to the ones in CASSANDRA-3681.

On Thu, Jan 12, 2012 at 5:36 AM, Sylvain Lebresne <sylv...@datastax.com> wrote:
> It's a new year, quite a bunch of fixes since 1.0.6, feels like it's time to
> do a new release. I thus propose the following artifacts for release as 1.0.7.
>
> Git: 
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.0.7-tentative
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/1.0.7/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-057/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> Note that I had to adapt a little bit to the switch to git. In particular,
> instead of using sha1 to mark the tentative commit of a release, I've decided
> to use a lightweight tag, namely 1.0.7-tentative. My goal being that once the
> vote passes, I'll delete this temporary tag and create the actual
> cassandra-1.0.7 tag. My rational for not creating the final tag right away is
> that:
>  - I want it to be clear 1.0.7 is not yet released
>  - If the vote fails, we would have to delete the tag anyway
> If someone has a problem with that, let me know.
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/UTfwn (CHANGES.txt)
> [2]: http://goo.gl/EHlRp (NEWS.txt)



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

Reply via email to