15005 I will take a different approach, because I cannot
plan to use Cassandra in my environment if I cannot assume anything at all
about when releases will be made.
Thanks!
ajs6f
> On Jul 8, 2019, at 12:37 PM, Michael Shuler wrote:
>
> On 7/3/19 1:44 PM, aj...@apache.org wrote:
>>
this list, but I haven't been
able to get a sense of how long it might be.
ajs6f
On Wed, Jul 3, 2019, 1:28 AM Mick Semb Wever mailto:m...@apache.org>> wrote:
> Is there any chance to get CASSANDRA-15005 (ready, with PR) into a
> 3.11.5 release?
I doubt it Soroka. It's no
tever I can to help
this happen. The current branch for 15005 is for 4.x, but it was originally
written by Jon Meredith for 3.x and I could easily move it back to that line.
Thanks!
ajs6f
> On Jul 2, 2019, at 6:23 AM, Mick Semb Wever wrote:
>
>
>> I will try and wrap up my r
+1 in the fullest degree. A date that needs to be changed is still enormously
more attractive than no date at all.
Adam Soroka
> On May 23, 2019, at 12:01 PM, Sumanth Pasupuleti
> wrote:
>
> Having at least a ballpark target on the website will definitely help. +1
> on setting it to Q4 2019 f
ocumentation. Thanks Jon Meredith!
ajs6f
[1]
https://cassandra.apache.org/doc/latest/development/patches.html#choosing-the-right-branches-to-work-on
[2] https://github.com/ajs6f/cassandra/blob/CASSANDRA-15005-trunk
> On Mar 15, 2019, at 1:12 PM, Jon Meredith wrote:
>
> I don’t think it
