Sorry but I'm (binding) -1 on this because of https://issues.apache.org/jira/browse/CASSANDRA-12236.
I disagree that knowingly releasing a version that will temporarily break in-flight queries during upgrade, even if it's for a very short time-frame until re-connection, is ok. I'll note in particular that in the test report, there is 74! failures in the upgrade tests (for reference the 3.7 test report had only 2 upgrade tests failure both with open tickets). Given that we have a known problem during upgrade, I don't really buy the "We are assuming these are due to a recent downsize in instance size that these tests run on" and that suggest to me the problem is not too minor. On Thu, Jul 21, 2016 at 6:18 AM, Dave Brosius <dbros...@mebigfatguy.com> wrote: > +1 > > > On 07/20/2016 05:48 PM, Michael Shuler wrote: > >> I propose the following artifacts for release as 3.8. >> >> sha1: c3ded0551f538f7845602b27d53240cd8129265c >> Git: >> >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative >> Artifacts: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-1123/org/apache/cassandra/apache-cassandra/3.8/ >> Staging repository: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-1123/ >> >> The debian packages are available here: >> http://people.apache.org/~mshuler/ >> >> The vote will be open for 72 hours (longer if needed). >> >> [1]: http://goo.gl/oGNH0i (CHANGES.txt) >> [2]: http://goo.gl/KjMtUn (NEWS.txt) >> [3]: https://goo.gl/TxVLKo (3.8 Test Summary) >> >> >
