Re: Time for a new 3.0/3.11 release?

2019-07-03 Thread ajs6f
In fact there is a branch for it noted in the ticket, from which a patch could be cut instantly, but there doesn't seem to be any point to doing that until the feature freeze is over. Is there any sense of timing on that? I've seen a few discussions about release process for 4.x on this list,

Re: Time for a new 3.0/3.11 release?

2019-07-03 Thread Jay Zhuang
I'd like to raise some attention for the following 2 tickets, they're patch-ready and deployed on all our production clusters: * CASSANDRA-15098: "Endpoints no longer owning tokens are not removed for vnode" For vNode cluster, the replaced node may not be removed from gossiper (and system.peers,