Re: [DISCUSS] releasing next 3.0 & 3.11

2019-01-16 Thread Michael Shuler
On 1/16/19 1:05 PM, Jonathan Haddad wrote: > Ping on this. https://issues.apache.org/jira/browse/CASSANDRA-14970 I could just punt and use what we've got with md5,sha1 checksums, then toss sha256,sha512 checksums in dist repo, when we're done. It's not pretty, but would work for me. That method

Re: [DISCUSS] releasing next 3.0 & 3.11

2019-01-16 Thread Rahul Singh
I’m all for it. Apart from general testing with an existing app, do we have automation to bring up / run stress / tear down the cluster? I have a few endurance tests I can run written on Gatling. Rahul Singh Chief Executive Officer m 202.905.2818 Anant Corporation 1010 Wisconsin Ave NW, Suite

Re: [DISCUSS] releasing next 3.0 & 3.11

2019-01-16 Thread Jonathan Haddad
Ping on this. On Mon, Jan 7, 2019 at 5:58 PM Michael Shuler wrote: > No problem, thanks for asking :) > > Michael > > On 1/7/19 6:20 PM, Jonathan Haddad wrote: > > It's been 5 months and 30+ bug fixes to each branch. > > > > Here's the two changelogs: > > > >

Re: [DISCUSS] releasing next 3.0 & 3.11

2019-01-07 Thread Michael Shuler
No problem, thanks for asking :) Michael On 1/7/19 6:20 PM, Jonathan Haddad wrote: > It's been 5 months and 30+ bug fixes to each branch. > > Here's the two changelogs: > > https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt >