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 would mean zero sharing of
release duty, since the artifacts live on one person's workstation,
instead of published where they can be downloaded.

I would appreciate some help with the ant targets. (it might be
something simple with mvn-install/publish target fixes, but I don't have
a massive amount of time to troubleshoot more. I did commit the release
target fix.

-- 
Michael

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



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 250
Washington, D.C. 20007

We build and manage digital business technology platforms.
On Jan 16, 2019, 1:05 PM -0600, Jonathan Haddad , wrote:
> 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:
> > >
> > > https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt
> > > https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt
> > >
> > > How's everyone feel about getting a release out this week / early next
> > > week? Some of these bugs are show stoppers, causing OOMs and data loss.
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>
> --
> Jon Haddad
> http://www.rustyrazorblade.com
> twitter: rustyrazorblade


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:
> >
> > https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt
> > https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt
> >
> > How's everyone feel about getting a release out this week / early next
> > week?  Some of these bugs are show stoppers, causing OOMs and data loss.
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

-- 
Jon Haddad
http://www.rustyrazorblade.com
twitter: rustyrazorblade


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
> https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt
> 
> How's everyone feel about getting a release out this week / early next
> week?  Some of these bugs are show stoppers, causing OOMs and data loss.
> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org