One of the reasons it is so long is because there are quite a few duplicate
entries.

* (Hadoop) support authentication in CqlRecordReader (CASSANDRA-7221)
 * (Hadoop) Close java driver Cluster in CQLRR.close (CASSANDRA-7228)
 * Fix potential SlabAllocator yield-starvation (CASSANDRA-7133)
 * Warn when 'USING TIMESTAMP' is used on a CAS BATCH (CASSANDRA-7067)
 * Starting threads in OutboundTcpConnectionPool constructor causes
race conditions (CASSANDRA-7177)
 * return all cpu values from BackgroundActivityMonitor.readAndCompute
(CASSANDRA-7183)
 * fix c* launch issues on Russian os's due to output of linux 'free'
cmd (CASSANDRA-6162)
 * Fix disabling autocompaction (CASSANDRA-7187)
 * Fix potential NumberFormatException when deserializing IntegerType
(CASSANDRA-7088)
 * cqlsh can't tab-complete disabling compaction (CASSANDRA-7185)
 * cqlsh: Accept and execute CQL statement(s) from command-line
parameter (CASSANDRA-7172)
 * Fix IllegalStateException in CqlPagingRecordReader (CASSANDRA-7198)
 * Fix the InvertedIndex trigger example (CASSANDRA-7211)


+1 from me though.

Gary.


On Wed, May 21, 2014 at 8:19 AM, Sylvain Lebresne <sylv...@datastax.com>wrote:

> Since we closed the first try we've fixed even more bugs, with notable
> things
> like CASSANDRA-6285. In any case, that changelog is getting pretty damn
> long so
> I propose the following artifacts for release as 2.0.8.
>
> sha1: 484d2816940cd2eb22d2365fcb376dd27e059e2e
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.8-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1012/org/apache/cassandra/apache-cassandra/2.0.8/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1012/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~slebresne/
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/EE3aHy (CHANGES.txt)
> [2]: http://goo.gl/dkl3Yu (NEWS.txt)
>

Reply via email to