Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real problem.
On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams <dri...@gmail.com> wrote: > +1 > > > On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne <sylv...@datastax.com>wrote: > >> So now that CASSANDRA-6485 has been committed, I propose the following >> artifacts for release as 1.2.13. >> >> sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9 >> Git: >> >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative >> Artifacts: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-050/org/apache/cassandra/apache-cassandra/1.2.13/ >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-050/ >> >> The artifacts as well as the debian package are also available here: >> http://people.apache.org/~slebresne/ >> >> Since it is a re-roll, I propose an expedited vote so the vote will be >> open >> for 24 hours (but longer if needed). >> >> [1]: http://goo.gl/j4xUAK (CHANGES.txt) >> [2]: http://goo.gl/iu5Og9 (NEWS.txt) >> > >