Thanks very much for this information-- it is indeed very helpful. This
statement:
> Indeed, the trunk branch has been frozen for new feature inclusion for quite
> some time, and there have been some limited discussions on how long this
> might be. "When it's done" is basically the current
On 7/3/19 1:44 PM, aj...@apache.org wrote:
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
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,
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,
> Is there any chance to get CASSANDRA-15005 (ready, with PR) into a
> 3.11.5 release?
I doubt it Soroka. It's not a bug and there's no patch for it, so I'd see no
reason why Michael would wait for this when he generously finds time to cut a
release.
Maybe the author and reviewer
Is there any chance to get CASSANDRA-15005 (ready, with PR) into a 3.11.5
release? I understand that there is a feature freeze, but I do see some small
tickets (eg. CASSANDRA-15090) that would seem to have been merged for release,
and I think 15005 is quite small, too. I'm happy to do whatever
> I will try and wrap up my review of 14812 today.
CASSANDRA-14812 has been committed.
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
It would also be good to include CASSANDRA-15193 (which I only just created,
sorry), as the counterpart to CASSANDRA-15176. I have a patch for this mostly
done and will post it in the next day or two.
> On 2 Jul 2019, at 07:13, Mick Semb Wever wrote:
>
>> It would be nice to have time to get
> It would be nice to have time to get CASSANDRA-14812 in
Yes.
I will try and wrap up my review of 14812 today. Another pair of eyes is
always welcome, especially anyone with experience on the various
StoppingTransformation usages.
regards,
Mick
It would be nice to have time to get CASSANDRA-14812 in, as it was also
(consciously) missed from the last release, and struggled to find a reviewer
since. Mick kindly found time to take a look while I was away. It’s a bit
rough to force affected users to wait another lengthy release cycle
On 7/1/19 3:32 PM, Blake Eggleston wrote:
Any objections to doing a new 3.0 and 3.11 release? Both branches
have accumulated a decent number of changes since their last release,
the highlights being improved merkle tree footprint, a gossip race,
and a handful of 2.1 -> 3.x upgrade bugs.
I was
Hi dev@,
Any objections to doing a new 3.0 and 3.11 release? Both branches have
accumulated a decent number of changes since their last release, the highlights
being improved merkle tree footprint, a gossip race, and a handful of 2.1 ->
3.x upgrade bugs.
Thanks,
Blake
12 matches
Mail list logo
