> 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 decide
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
> 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 C
